diff --git a/locale/da/LC_MESSAGES/administration.po b/locale/da/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/da/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/da/LC_MESSAGES/essentials.po b/locale/da/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/da/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/da/LC_MESSAGES/hr.po b/locale/da/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/da/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/da/LC_MESSAGES/studio.po b/locale/da/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/da/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/de/LC_MESSAGES/administration.po b/locale/de/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/de/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/de/LC_MESSAGES/essentials.po b/locale/de/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/de/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/de/LC_MESSAGES/hr.po b/locale/de/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/de/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/de/LC_MESSAGES/studio.po b/locale/de/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/de/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/es/LC_MESSAGES/administration.po b/locale/es/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/es/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/es/LC_MESSAGES/essentials.po b/locale/es/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/es/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/es/LC_MESSAGES/hr.po b/locale/es/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/es/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/es/LC_MESSAGES/studio.po b/locale/es/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/es/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/fr/LC_MESSAGES/administration.po b/locale/fr/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/fr/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/fr/LC_MESSAGES/essentials.po b/locale/fr/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/fr/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/fr/LC_MESSAGES/hr.po b/locale/fr/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/fr/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/fr/LC_MESSAGES/studio.po b/locale/fr/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/fr/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/nl/LC_MESSAGES/administration.po b/locale/nl/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/nl/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/nl/LC_MESSAGES/essentials.po b/locale/nl/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/nl/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/nl/LC_MESSAGES/hr.po b/locale/nl/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/nl/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/nl/LC_MESSAGES/studio.po b/locale/nl/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/nl/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/pt_BR/LC_MESSAGES/administration.po b/locale/pt_BR/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/pt_BR/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/pt_BR/LC_MESSAGES/essentials.po b/locale/pt_BR/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/pt_BR/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/pt_BR/LC_MESSAGES/hr.po b/locale/pt_BR/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/pt_BR/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/pt_BR/LC_MESSAGES/studio.po b/locale/pt_BR/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/pt_BR/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/administration.po b/locale/ru/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/ru/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/ru/LC_MESSAGES/essentials.po b/locale/ru/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/ru/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/hr.po b/locale/ru/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/ru/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/ru/LC_MESSAGES/studio.po b/locale/ru/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/ru/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/uk/LC_MESSAGES/administration.po b/locale/uk/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/uk/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/uk/LC_MESSAGES/essentials.po b/locale/uk/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/uk/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/uk/LC_MESSAGES/hr.po b/locale/uk/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/uk/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/uk/LC_MESSAGES/studio.po b/locale/uk/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/uk/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/administration.po b/locale/zh_CN/LC_MESSAGES/administration.po new file mode 100644 index 0000000000..d6d006d3f6 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/administration.po @@ -0,0 +1,7934 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/administration.rst:8 +#: ../../content/administration/odoo_online.rst:20 +msgid "Database management" +msgstr "" + +#: ../../content/administration.rst:10 +msgid "" +"These guides provide instructions on how to install, maintain and upgrade " +"Odoo databases." +msgstr "" + +#: ../../content/administration.rst:13 +msgid ":doc:`History of Versions `" +msgstr "" + +#: ../../content/administration.rst:16 +#: ../../content/administration/on_premise/geo_ip.rst:9 +msgid "Installation" +msgstr "" + +#: ../../content/administration.rst:18 +msgid "" +"Depending on the intended use case, there are multiple ways to install Odoo " +"- or not install it at all." +msgstr "" + +#: ../../content/administration.rst:21 +msgid "" +":doc:`Online ` is the easiest way to use Odoo in" +" production or to try it." +msgstr "" + +#: ../../content/administration.rst:23 +msgid "" +":doc:`Packaged installers ` are suitable" +" for testing Odoo and developing modules. They can be used for long-term " +"production with additional deployment and maintenance work." +msgstr "" + +#: ../../content/administration.rst:27 +msgid "" +":doc:`Source install ` provides greater " +"flexibility, as it allows, for example, running multiple Odoo versions on " +"the same system. It is adequate to develop modules and can be used as a base" +" for production deployment." +msgstr "" + +#: ../../content/administration.rst:31 +msgid "" +"A `Docker `_ base image is available for " +"development or deployment." +msgstr "" + +#: ../../content/administration.rst:37 +msgid "Editions" +msgstr "" + +#: ../../content/administration.rst:39 +msgid "There are two different editions." +msgstr "" + +#: ../../content/administration.rst:41 +msgid "" +"**Odoo Community** is the free and open-source version of the software, " +"licensed under the `GNU LGPLv3 " +"`_. It is the core upon " +"which Odoo Enterprise is built." +msgstr "" + +#: ../../content/administration.rst:45 +msgid "" +"**Odoo Enterprise** is the shared source version of the software, giving " +"access to more functionalities, including functional support, upgrades, and " +"hosting. `Pricing `_ starts from one app " +"free." +msgstr "" + +#: ../../content/administration.rst:50 +msgid "" +":doc:`Switch from Community to Enterprise " +"` at any time (except for" +" the source install)." +msgstr "" + +#: ../../content/administration/hosting.rst:3 +msgid "Hosting" +msgstr "" + +#: ../../content/administration/hosting.rst:8 +msgid "Change hosting solution" +msgstr "" + +#: ../../content/administration/hosting.rst:10 +msgid "" +"The instructions to change the hosting type of a database depend on the " +"current solution used and to which solution the database should be moved." +msgstr "" + +#: ../../content/administration/hosting.rst:14 +msgid "Transferring an on-premise database" +msgstr "" + +#: ../../content/administration/hosting.rst:17 +#: ../../content/administration/hosting.rst:92 +msgid "To Odoo Online" +msgstr "" + +#: ../../content/administration/hosting.rst:20 +#: ../../content/administration/hosting.rst:95 +msgid "Odoo Online is *not* compatible with **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:21 +msgid "" +"The database's current version must be :doc:`supported " +"`." +msgstr "" + +#: ../../content/administration/hosting.rst:23 +msgid "Create a :ref:`duplicate of the database `." +msgstr "" + +#: ../../content/administration/hosting.rst:24 +msgid "In this duplicate, uninstall all **non-standard apps**." +msgstr "" + +#: ../../content/administration/hosting.rst:25 +msgid "Use the database manager to grab a *dump with filestore*." +msgstr "" + +#: ../../content/administration/hosting.rst:26 +#: ../../content/administration/hosting.rst:98 +msgid "" +"`Create a support ticket `_ including the " +"following:" +msgstr "" + +#: ../../content/administration/hosting.rst:28 +#: ../../content/administration/hosting.rst:100 +msgid "your **subscription number**," +msgstr "" + +#: ../../content/administration/hosting.rst:29 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`), and" +msgstr "" + +#: ../../content/administration/hosting.rst:30 +msgid "" +"the **dump** as an attachment or as a link to the file (required for 60 MB+ " +"files)." +msgstr "" + +#: ../../content/administration/hosting.rst:32 +#: ../../content/administration/hosting.rst:107 +msgid "" +"Odoo then makes sure the database is compatible before putting it online. In" +" case of technical issues during the process, Odoo might contact you." +msgstr "" + +#: ../../content/administration/hosting.rst:36 +#: ../../content/administration/hosting.rst:111 +msgid "" +"If you have time constraints, `create a support ticket " +"`_ as soon as possible to schedule the " +"transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:40 +#: ../../content/administration/hosting.rst:78 +msgid "To Odoo.sh" +msgstr "" + +#: ../../content/administration/hosting.rst:42 +#: ../../content/administration/hosting.rst:85 +msgid "" +"Follow the instructions found in :ref:`the Import your database section " +"` of the Odoo.sh *Create your project* " +"documentation." +msgstr "" + +#: ../../content/administration/hosting.rst:46 +msgid "Transferring an Odoo Online database" +msgstr "" + +#: ../../content/administration/hosting.rst:49 +msgid "" +"Odoo Online's :ref:`intermediary versions ` are not " +"supported by Odoo.sh or on-premise. Therefore, if the database to transfer " +"is running an intermediary version, it must be upgraded first to the next " +":ref:`major version `, waiting for its release if " +"necessary." +msgstr "" + +#: ../../content/administration/hosting.rst:55 +msgid "" +"Transferring an online database running on Odoo 16.3 would require first " +"upgrading it to Odoo 17.0." +msgstr "" + +#: ../../content/administration/hosting.rst:59 +msgid "" +"Click the :icon:`fa-gear` (:guilabel:`gear`) button next to the database " +"name on the `Odoo Online database manager " +"`_ to display its version number." +msgstr "" + +#: ../../content/administration/hosting.rst:63 +msgid "" +"If there is an active Odoo subscription linked to the database being " +"migrated, reach out to the Customer Service Manager or `contact Odoo support" +" `_ to complete the subscription transfer." +msgstr "" + +#: ../../content/administration/hosting.rst:68 +#: ../../content/administration/hosting.rst:120 +msgid "To on-premise" +msgstr "" + +#: ../../content/administration/hosting.rst:70 +#: ../../content/administration/hosting.rst:80 +msgid "" +"Download a database backup by signing in to `the Odoo Online database " +"manager `_, clicking the :icon:`fa-gear`" +" (:guilabel:`gear`) button next to the database name, then selecting " +":icon:`fa-cloud-download` :guilabel:`Download`. If the download fails due to" +" the file being too large, `contact Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/hosting.rst:75 +#: ../../content/administration/hosting.rst:123 +msgid "" +"Restore the database from the database manager on your local server using " +"the backup." +msgstr "" + +#: ../../content/administration/hosting.rst:89 +msgid "Transferring an Odoo.sh database" +msgstr "" + +#: ../../content/administration/hosting.rst:97 +msgid "" +"Uninstall all **non-standard apps** in a staging build before doing it in " +"the production build." +msgstr "" + +#: ../../content/administration/hosting.rst:101 +msgid "" +"the **URL** you want to use for the database (e.g., `company.odoo.com`)," +msgstr "" + +#: ../../content/administration/hosting.rst:102 +msgid "which **branch** should be migrated," +msgstr "" + +#: ../../content/administration/hosting.rst:103 +msgid "" +"in which **region** you want the database to be hosted (Americas, Europe, or" +" Asia)," +msgstr "" + +#: ../../content/administration/hosting.rst:104 +msgid "which user(s) will be the **administrator(s)**, and" +msgstr "" + +#: ../../content/administration/hosting.rst:105 +msgid "" +"**when** (and in which timezone) you want the database to be up and running." +msgstr "" + +#: ../../content/administration/hosting.rst:113 +msgid "Select the **region** closest to most of your users to reduce latency." +msgstr "" + +#: ../../content/administration/hosting.rst:114 +msgid "Future **administrator(s)** must have an Odoo.com account." +msgstr "" + +#: ../../content/administration/hosting.rst:115 +msgid "" +"The **date and time** you want the database to be up and running are helpful" +" to organize the switch from the Odoo.sh server to the Odoo Online servers." +msgstr "" + +#: ../../content/administration/hosting.rst:117 +msgid "Databases are **not reachable** during their migration." +msgstr "" + +#: ../../content/administration/hosting.rst:122 +msgid "" +"Download a :ref:`backup of your Odoo.sh production database " +"`." +msgstr "" + +#: ../../content/administration/mobile.rst:3 +msgid "Odoo mobile apps" +msgstr "" + +#: ../../content/administration/mobile.rst:5 +msgid "" +"Two kind of Odoo mobile app exist: the progressive web app (PWA) and store " +"apps. Using the PWA is recommended." +msgstr "" + +#: ../../content/administration/mobile.rst:9 +msgid "Progressive web app (PWA)" +msgstr "" + +#: ../../content/administration/mobile.rst:11 +msgid "" +"PWAs are web-based applications designed to function across different " +"devices and platforms, leveraging web browsers to deliver user experiences " +"similar to native apps." +msgstr "" + +#: ../../content/administration/mobile.rst:14 +msgid "The Odoo PWA features include:" +msgstr "" + +#: ../../content/administration/mobile.rst:16 +msgid "Quick access by adding the PWA to a device's home screen" +msgstr "" + +#: ../../content/administration/mobile.rst:17 +msgid "Seamless and borderless navigation experience" +msgstr "" + +#: ../../content/administration/mobile.rst:18 +msgid "Push notifications" +msgstr "" + +#: ../../content/administration/mobile.rst:19 +msgid "SSO authentication" +msgstr "" + +#: ../../content/administration/mobile.rst:21 +msgid "" +"To install the Odoo PWA, launch a browser supporting PWAs, and sign in to an" +" Odoo database. The instructions to install a PWA depend on the platform and" +" browser used." +msgstr "" + +#: ../../content/administration/mobile.rst:26 +msgid "Android" +msgstr "" + +#: ../../content/administration/mobile.rst:28 +msgid "" +"**Chrome**: open Chrome's menu (:guilabel:`⋮`), select :guilabel:`Install " +"app`, and tap :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:31 +msgid "" +"**Firefox**: open Firefox's menu (:guilabel:`⋮`), select " +":guilabel:`Install`, and either touch and hold the Odoo icon or tap " +":guilabel:`Add automatically`." +msgstr "" + +#: ../../content/administration/mobile.rst:34 +msgid "" +"The PWA can also be installed with **Samsung Internet**, **Edge**, and " +"**Opera**." +msgstr "" + +#: ../../content/administration/mobile.rst:36 +msgid "iOS" +msgstr "" + +#: ../../content/administration/mobile.rst:38 +msgid "" +"**Safari**: open the **Share** menu by tapping the square with an arrow " +"pointing upwards icon, select :guilabel:`Add to Home Screen`, edit the PWA " +"details if desired, and tap :guilabel:`Add`." +msgstr "" + +#: ../../content/administration/mobile.rst:42 +msgid "" +"On iOS 16.4 and above, the PWA can also be installed with **Chrome**, " +"**Firefox**, and **Edge**." +msgstr "" + +#: ../../content/administration/mobile.rst:45 +msgid "Desktop" +msgstr "" + +#: ../../content/administration/mobile.rst:47 +msgid "" +"**Chrome** and **Edge**: click the installation icon at the right of the " +"address bar and click :guilabel:`Install`." +msgstr "" + +#: ../../content/administration/mobile.rst:51 +msgid "" +"`Google Chrome Help: Use progressive web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:53 +msgid "" +"`MDN Web Docs: Installing and uninstalling web apps " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:55 +msgid "" +"`Microsoft Support: Install, manage, or uninstall apps in Microsoft Edge " +"`_" +msgstr "" + +#: ../../content/administration/mobile.rst:58 +msgid "Store apps" +msgstr "" + +#: ../../content/administration/mobile.rst:60 +msgid "" +"The Odoo mobile apps are available for download on the `Google Play Store " +"`_ and `Apple" +" App Store `_." +msgstr "" + +#: ../../content/administration/mobile.rst:65 +msgid "" +"The iOS app might not be updated and might be deprecated at some point in " +"the future." +msgstr "" + +#: ../../content/administration/mobile.rst:67 +msgid "" +"While the store apps support multi-accounts, they are not compatible with " +"SSO authentication." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:3 +msgid "Neutralized database" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:5 +msgid "" +"A neutralized database is a non-production database on which several " +"parameters are deactivated. This enables one to carry out tests without the " +"risk of launching specific automated processes that could impact production " +"data (e.g., sending emails to customers). Live access is removed and turned " +"into a testing environment." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:11 +msgid "**Any testing database created is a neutralized database:**" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:13 +msgid "testing backup databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:14 +msgid "duplicate databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:15 +msgid "for Odoo.sh: staging and development databases" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:18 +msgid "" +"A database can also be neutralized when upgrading, as it is vital to do some" +" tests before switching to a new version." +msgstr "" + +#: ../../content/administration/neutralized_database.rst:22 +msgid "Deactivated features" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:24 +msgid "Here is a non-exhaustive list of the deactivated features:" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:26 +msgid "" +"all planned actions (e.g., automatic invoicing of subscriptions, mass " +"mailing, etc.)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:27 +msgid "outgoing emails" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:28 +msgid "bank synchronization" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:29 +msgid "payment providers" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:30 +msgid "delivery methods" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:31 +msgid ":abbr:`IAP (In-App Purchase)` tokens" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:32 +msgid "website visibility (prevent search engines from indexing your site)" +msgstr "" + +#: ../../content/administration/neutralized_database.rst:35 +msgid "" +"**A red banner at the top of the screen is displayed on the neutralized " +"database so that it can be seen immediately.**" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:3 +msgid "Odoo.com accounts" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:5 +msgid "" +"This document describes how to edit and manage an Odoo.com account, " +"including adding a client database, deleting an account, resetting a " +"password, and enabling two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:9 +msgid "Grant users access to database" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:11 +msgid "" +"A database can be linked to an Odoo.com account that was created by a " +"different Odoo.com account. This allows the database to appear in the *My " +"Databases* page of the account. To do so, the client Odoo.com account needs " +"to be added to the database as a user." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:15 +msgid "" +"First, sign in to the Odoo.com account that created the client database. In " +"the main Odoo dashboard of the database, navigate to the **Settings** app, " +"and click :guilabel:`Manage Users` in the :guilabel:`Users` section. Click " +"the :guilabel:`New` button, and enter a name in the :guilabel:`Name` field " +"for this user. Next, enter the email address used to register the desired " +"Odoo.com account in the :guilabel:`Email` field. Navigate back to " +":guilabel:`Settings` using the breadcrumbs, and a pop-up window titled " +":guilabel:`Users Invitations` appears, with a warning that adding additional" +" users will increase the amount of the subscription." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:23 +msgid "" +"Click :guilabel:`Confirm`, and the :guilabel:`Users` list appears. An " +"invitation is automatically sent to the email address. Once confirmed, the " +"client database now appears in the **My Databases** page of the target " +"Odoo.com account." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:28 +msgid "" +"To provide full access to the database for this user, set the " +":guilabel:`Dashboard` field under the :guilabel:`Productivity` header to " +":guilabel:`Admin`. Next, set the :guilabel:`Administration` field under the " +":guilabel:`Administration` header to :guilabel:`Settings`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:34 +msgid "Delete Odoo.com account" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:36 +msgid "" +"To delete an Odoo.com account, start by clicking the profile icon in the " +"upper-right corner (represented by the username and icon) to reveal a drop-" +"down menu. From the drop-down menu, select :guilabel:`My Odoo.com account`, " +"which reveals the user portal." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:40 +msgid "" +"From the user portal, the delete option can be accessed by going to " +":menuselection:`My Account --> Edit Security Settings --> Delete Account`. " +"It can also be accessed by going to `https://www.odoo.com/my/home " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:45 +msgid "" +"Deleting an Odoo account is irreversible. Be careful performing this action," +" as the Odoo.com account is **not** retrievable once deleted." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:48 +msgid "" +"Upon clicking the :guilabel:`Delete Account` button, a pop-up window " +"appears, requesting confirmation for the account deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:-1 +msgid "" +"Clicking on the Delete Account button will populate a window verifying the " +"change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:55 +msgid "" +"To confirm the deletion, enter the :guilabel:`Password` and the " +":guilabel:`Login` for the account being deleted. Then, click the " +":guilabel:`Delete Account` button to confirm the deletion." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:61 +msgid "Odoo.com account password change" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:63 +msgid "" +"To change an Odoo.com account password, first login into the Odoo.com user " +"account from the Odoo.com login page. After logging-in, go to the upper-" +"right corner of the screen, and click the :guilabel:`▼ (down arrow)` icon " +"next to the profile icon. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:68 +msgid "" +"To change the Odoo.com password, click on the :guilabel:`Edit Security " +"Settings` link, below the :menuselection:`Account Security` section. Next, " +"make the necessary changes by typing in the current :guilabel:`Password`, " +":guilabel:`New Password`, and verify the new password. Lastly, click on " +":guilabel:`Change Password` to complete the password change." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:74 +msgid "" +"If a customer would like to change the login, contact Odoo support `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:78 +msgid "" +"Passwords for Odoo.com users and portal users remain separate, even if the " +"same email address is used." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:82 +msgid "Add two-factor authentication" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:84 +msgid "" +"To add two-factor authentication, login into the Odoo.com user account from " +"the Odoo.com login page. After logging-in, go to the upper-right corner of " +"the screen, and click the :guilabel:`▼ (down arrow)` icon next to the " +":guilabel:`profile icon`. Then, select :guilabel:`My Account`, and a portal " +"dashboard appears." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:89 +msgid "" +"If the user would like to turn on two-factor authentication (2FA) for " +"Odoo.com access, click on the :guilabel:`Edit Security Settings` link below " +"the :menuselection:`Account Security` section." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:92 +msgid "" +"Click on :guilabel:`Enable two-factor authentication` to turn on :abbr:`2FA " +"(two-factor authentication)`. Then, confirm the current password in the " +":guilabel:`Password` field. Next, click on :guilabel:`Confirm Password`. " +"Following that, activate :abbr:`2FA (two-factor authentication)` in a " +":abbr:`2FA (two-factor authentication)` app (Google Authenticator, Authy, " +"etc.), by scanning the :guilabel:`QR code` or entering a " +":guilabel:`Verification Code`." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:98 +msgid "" +"Finally, click on :guilabel:`Enable two-factor authentication` to complete " +"the setup." +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:101 +msgid "" +"Under :guilabel:`My Account` Odoo.com users can also access the following:" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:103 +msgid ":guilabel:`My Partner dashboard`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:104 +msgid ":guilabel:`My In-App Services`" +msgstr "" + +#: ../../content/administration/odoo_accounts.rst:105 +msgid ":guilabel:`My Apps Dashboard`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:3 +#: ../../content/administration/supported_versions.rst:29 +#: ../../content/administration/upgrade.rst:14 +#: ../../content/administration/upgrade.rst:109 +#: ../../content/administration/upgrade.rst:337 +msgid "Odoo Online" +msgstr "" + +#: ../../content/administration/odoo_online.rst:5 +msgid "" +"`Odoo Online `_ provides private databases which" +" are fully managed and hosted by Odoo. It can be used for long-term " +"production or to test Odoo thoroughly, including customizations that don't " +"require code." +msgstr "" + +#: ../../content/administration/odoo_online.rst:10 +msgid "Odoo Online is incompatible with custom modules or the Odoo App Store." +msgstr "" + +#: ../../content/administration/odoo_online.rst:12 +msgid "" +"Odoo Online databases are accessed using any web browser and do not require " +"a local installation." +msgstr "" + +#: ../../content/administration/odoo_online.rst:14 +msgid "" +"To quickly try out Odoo, shared `demo `_ instances " +"are available. No registration is required, but each instance only lives for" +" a few hours." +msgstr "" + +#: ../../content/administration/odoo_online.rst:22 +msgid "" +"To manage a database, go to the `database manager " +"`_ and sign in as the database " +"administrator." +msgstr "" + +#: ../../content/administration/odoo_online.rst:25 +msgid "" +"All the main database management options are available by clicking the " +"database name, except the upgrade option, which can be accessed by clicking " +"the **arrow in a circle** icon next to the database name. It is only " +"displayed if an upgrade is available." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Accessing the database management options" +msgstr "" + +#: ../../content/administration/odoo_online.rst:32 +msgid ":ref:`odoo_online/upgrade`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:33 +msgid ":ref:`odoo_online/duplicate`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:34 +msgid ":ref:`odoo_online/rename`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:35 +msgid ":ref:`odoo_online/download`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:36 +msgid ":ref:`odoo_online/domains`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:37 +msgid ":ref:`odoo_online/tags`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:38 +msgid ":ref:`odoo_online/delete`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:39 +msgid ":ref:`odoo_online/contact-support`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:40 +msgid ":ref:`odoo_online/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:41 +msgid ":ref:`odoo_online/web-services`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:46 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:293 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:123 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:168 +#: ../../content/administration/upgrade.rst:3 +msgid "Upgrade" +msgstr "" + +#: ../../content/administration/odoo_online.rst:48 +msgid "Trigger a database upgrade." +msgstr "" + +#: ../../content/administration/odoo_online.rst:51 +msgid "" +"For more information about the upgrade process, check out the :ref:`Odoo " +"Online upgrade documentation `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:57 +msgid "Duplicate" +msgstr "" + +#: ../../content/administration/odoo_online.rst:59 +msgid "" +"Create an exact copy of the database, which can be used to perform testing " +"without compromising daily operations." +msgstr "" + +#: ../../content/administration/odoo_online.rst:63 +msgid "" +"By checking :guilabel:`For testing purposes`, all external actions (emails, " +"payments, delivery orders, etc.) are disabled by default on the duplicated " +"database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:65 +msgid "Duplicated databases expire automatically after 15 days." +msgstr "" + +#: ../../content/administration/odoo_online.rst:66 +msgid "" +"A maximum of five duplicates can be made per database. Under extraordinary " +"circumstances, contact `support `_ to raise the " +"limit." +msgstr "" + +#: ../../content/administration/odoo_online.rst:72 +msgid "Rename" +msgstr "" + +#: ../../content/administration/odoo_online.rst:74 +msgid "Rename the database and its URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:79 +msgid "Download" +msgstr "" + +#: ../../content/administration/odoo_online.rst:81 +msgid "Download a ZIP file containing a backup of the database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:84 +msgid "" +"Databases are backed up daily as per the `Odoo Cloud Hosting SLA " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:86 +msgid "" +"If the :guilabel:`Download` option is disabled, it means your database is " +"too large to be downloaded through this method. In this case, please contact" +" `Odoo Support `_ to request an alternative " +"download solution." +msgstr "" + +#: ../../content/administration/odoo_online.rst:93 +msgid "Domain names" +msgstr "" + +#: ../../content/administration/odoo_online.rst:95 +msgid "" +"Use a custom :doc:`domain name " +"` to access the " +"database via another URL." +msgstr "" + +#: ../../content/administration/odoo_online.rst:99 +msgid "You can :ref:`register a domain name for free `." +msgstr "" + +#: ../../content/administration/odoo_online.rst:104 +msgid "Tags" +msgstr "" + +#: ../../content/administration/odoo_online.rst:106 +msgid "Add tags to easily identify and sort your databases." +msgstr "" + +#: ../../content/administration/odoo_online.rst:109 +msgid "You can search for tags in the search bar." +msgstr "" + +#: ../../content/administration/odoo_online.rst:114 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:550 +msgid "Delete" +msgstr "" + +#: ../../content/administration/odoo_online.rst:116 +msgid "Delete a database instantly." +msgstr "" + +#: ../../content/administration/odoo_online.rst:119 +msgid "" +"Deleting a database means that all data is permanently lost. The deletion is" +" instant and applies to all users. It is recommended to create a backup of " +"the database before deleting it." +msgstr "" + +#: ../../content/administration/odoo_online.rst:122 +msgid "" +"Carefully read the warning message and only proceed if the implications of " +"deleting a database are fully understood." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "The warning message displayed before deleting a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:129 +msgid "Only an administrator can delete a database." +msgstr "" + +#: ../../content/administration/odoo_online.rst:130 +msgid "The database name is immediately made available to anyone." +msgstr "" + +#: ../../content/administration/odoo_online.rst:131 +msgid "" +"Deleting a database if it has expired or is linked to a subscription is " +"impossible. In that case, contact `Odoo Support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_online.rst:137 +msgid "Contact us" +msgstr "" + +#: ../../content/administration/odoo_online.rst:139 +msgid "" +"Access the `Odoo.com support page `_ with the " +"database's details already pre-filled." +msgstr "" + +#: ../../content/administration/odoo_online.rst:145 +msgid "Invite / remove users" +msgstr "" + +#: ../../content/administration/odoo_online.rst:147 +msgid "" +"To invite users, fill out the new user's email address and click " +":guilabel:`Invite`. To add multiple users, click :guilabel:`Add more users`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:-1 +msgid "Inviting a user on a database" +msgstr "" + +#: ../../content/administration/odoo_online.rst:153 +msgid "To remove users, select them and click :guilabel:`Remove`." +msgstr "" + +#: ../../content/administration/odoo_online.rst:156 +msgid ":doc:`/applications/general/users`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:157 +msgid ":doc:`odoo_accounts`" +msgstr "" + +#: ../../content/administration/odoo_online.rst:162 +msgid "Web Services" +msgstr "" + +#: ../../content/administration/odoo_online.rst:164 +msgid "" +"In order to programmatically retrieve the list of the databases displayed in" +" the `database manager `_, call the " +"method `list` of the model `odoo.database` via a :doc:`Web Service " +"` call." +msgstr "" + +#: ../../content/administration/odoo_online.rst:168 +msgid "" +"Inspired from the examples provided in the :doc:`Web Services " +"` section, this is how to retrieve this list" +" with the library ``xmlrpc.client``::" +msgstr "" + +#: ../../content/administration/odoo_online.rst:181 +msgid "And here is the equivalent example with JSON-RPC::" +msgstr "" + +#: ../../content/administration/odoo_sh.rst:5 +#: ../../content/administration/supported_versions.rst:30 +#: ../../content/administration/upgrade.rst:22 +#: ../../content/administration/upgrade.rst:139 +#: ../../content/administration/upgrade.rst:348 +msgid "Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced.rst:5 +msgid "Advanced" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:4 +msgid "Containers" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:7 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:9 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:6 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:9 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:6 +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:9 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:6 +#: ../../content/administration/odoo_sh/getting_started/status.rst:6 +#: ../../content/administration/odoo_sh/overview.rst:5 +msgid "Overview" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:9 +msgid "" +"Each build is isolated within its own container (Linux namespaced " +"container)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:11 +msgid "" +"The base is an Ubuntu system, where all of Odoo's required dependencies, as " +"well as common useful packages, are installed." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:14 +msgid "" +"If your project requires additional Python dependencies, or more recent " +"releases, you can define a :file:`requirements.txt` file in the root of your" +" branches listing them. The platform will take care to install these " +"dependencies in your containers. `The pip requirements specifiers " +"`_ documentation can help you write a :file:`requirements.txt` " +"file. To have a concrete example, check out the `requirements.txt file of " +"Odoo `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:22 +msgid "" +"The :file:`requirements.txt` files of submodules are taken into account as " +"well. The platform looks for :file:`requirements.txt` files in each folder " +"containing Odoo modules: Not in the module folder itself, but in their " +"parent folder." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:27 +msgid "Directory structure" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:29 +msgid "" +"As the containers are Ubuntu based, their directory structure follows the " +"linux Filesystem Hierarchy Standard. `Ubuntu's filesystem tree overview " +"`_" +" explains the main directories." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:33 +msgid "Here are the Odoo.sh pertinent directories:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:73 +msgid "Both Python 2.7 and 3.5 are installed in the containers. However:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:75 +msgid "" +"If your project is configured to use Odoo 10.0, the Odoo server runs with " +"Python 2.7." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:76 +msgid "" +"If your project is configured to use Odoo 11.0 or above, the Odoo server " +"runs with Python 3.5." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:79 +msgid "Database shell" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:81 +msgid "" +"While accessing a container with the shell, you can access the database " +"using *psql*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:92 +msgid "" +"**Be careful !** `Use transactions " +"`_ " +"(*BEGIN...COMMIT/ROLLBACK*) for every *sql* statements leading to changes " +"(*UPDATE*, *DELETE*, *ALTER*, ...), especially for your production database." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:97 +msgid "" +"The transaction mechanism is your safety net in case of mistake. You simply " +"have to rollback your changes to revert your database to its previous state." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:100 +msgid "" +"For example, it may happen that you forget to set your *WHERE* condition." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:111 +msgid "" +"In such a case, you can rollback to revert the unwanted changes that you " +"just mistakenly did, and rewrite the statement:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:122 +msgid "" +"However, do not forget to either commit or rollback your transaction after " +"having done it. Open transactions may lock records in your tables and your " +"running database may wait for them to be released. It can cause a server to " +"hang indefinitely." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:126 +msgid "" +"In addition, when possible, use your staging databases to test your " +"statements first. It gives you an extra safety net." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:129 +msgid "Run an Odoo server" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:131 +msgid "" +"You can start an Odoo server instance from a container shell. You won't be " +"able to access it from the outside world with a browser, but you can for " +"instance:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:134 +msgid "use the Odoo shell," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:146 +msgid "install a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:152 +msgid "update a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:158 +msgid "run the tests for a module," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:164 +msgid "In the above commands, the argument:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:166 +msgid "``--without-demo=all`` prevents demo data to be loaded for all modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:167 +msgid "" +"``--stop-after-init`` will immediately shutdown the server instance after it" +" completed the operations you asked." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:169 +msgid "" +"More options are available and detailed in the :doc:`CLI documentation " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:172 +msgid "" +"You can find in the logs (*~/logs/odoo.log*) the addons path used by Odoo.sh" +" to run your server. Look for \"*odoo: addons paths*\":" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:181 +msgid "" +"**Be careful**, especially with your production database. Operations that " +"you perform running this Odoo server instance are not isolated: Changes will" +" be effective in the database. Always, make your tests in your staging " +"databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:186 +msgid "Debugging in Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:188 +msgid "" +"Debugging an Odoo.sh build is not really different than another Python app. " +"This article only explains the specificities and limitations of the Odoo.sh " +"platform, and assumes that you already know how to use a debugger." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:190 +msgid "" +"If you don't know how to debug a Python application yet, there are multiple " +"introductory courses that can be easily found on the Internet." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:192 +msgid "" +"You can use ``pdb``, ``pudb`` or ``ipdb`` to debug your code on Odoo.sh. As " +"the server is run outside a shell, you cannot launch the debugger directly " +"from your Odoo instance backend as the debugger needs a shell to operate." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:195 +msgid "" +"`pdb `_ is installed by default " +"in every container." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:197 +msgid "" +"If you want to use `pudb `_ or `ipdb " +"`_ you have to install it before." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:199 +msgid "To do so, you have two options:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:201 +msgid "temporary (only in the current build):" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:207 +msgid "or" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:213 +msgid "" +"permanent: add ``pudb`` or ``ipdb`` to your project ``requirements.txt`` " +"file." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:216 +msgid "" +"Then edit the code where you want to trigger the debugger and add this:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:224 +msgid "" +"The condition :code:`sys.__stdin__.isatty()` is a hack that detects if you " +"run Odoo from a shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:226 +msgid "Save the file and then run the Odoo Shell:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:232 +msgid "" +"Finally, *via* the Odoo Shell, you can trigger the piece of " +"code/function/method you want to debug." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/containers.rst:-1 +msgid "Console screenshot showing ``pdb`` running in an Odoo.sh shell." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:6 +msgid "Frequent Technical Questions" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:9 +msgid "\"Scheduled actions do not run at the exact time they were expected\"" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:11 +msgid "" +"On the Odoo.sh platform, we cannot guarantee an exact running time for " +"scheduled actions." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:13 +msgid "" +"This is due to the fact that there might be multiple customers on the same " +"server, and we must guarantee a fair share of the server for every customer." +" Scheduled actions are therefore implemented slightly differently than on a " +"regular Odoo server, and are run on a *best effort* policy." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:16 +msgid "" +"Do not expect any scheduled action to be run more often than every 5 min." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:19 +msgid "Are there \"best practices\" regarding scheduled actions?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:21 +msgid "" +"**Odoo.sh always limits the execution time of scheduled actions (*aka* " +"crons).** Therefore, you must keep this fact in mind when developing your " +"own crons." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:24 +msgid "We advise that:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:26 +msgid "Your scheduled actions should work on small batches of records." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:27 +msgid "" +"Your scheduled actions should commit their work after processing each batch;" +" this way, if they get interrupted by the time-limit, there is no need to " +"start over." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:29 +msgid "" +"Your scheduled actions should be `idempotent " +"`_: they must not cause side-" +"effects if they are started more often than expected." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:36 +msgid "How can I automate tasks when an IP address change occurs?" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:38 +msgid "" +"**Odoo.sh notifies project administrators of IP address changes.** " +"Additionally, when the IP address of a production instance changes, an HTTP " +"`GET` request is made to the path `/_odoo.sh/ip-change` with the new IP " +"address included as a query string parameter (`new`), along with the " +"previous IP address as an additional parameter (`old`)." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:43 +msgid "" +"This mechanism allows custom actions to be applied in response to the IP " +"address change (e.g., sending an email, contacting a firewall API, " +"configuring database objects, etc.)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:46 +msgid "" +"For security reasons, the `/_odoo.sh/ip-change` route is accessible only " +"internally by the platform itself and returns a `403` response if accessed " +"through any other means." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/frequent_technical_questions.rst:49 +msgid "Here is a pseudo-implementation example:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:6 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:249 +msgid "Submodules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:11 +msgid "" +"A `Git submodule `_ " +"allows you to integrate other Git projects into your code, without the need " +"to copy-paste all their code." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:14 +msgid "" +"Indeed, your custom modules can depend on modules from other repositories. " +"Regarding Odoo, this feature allows you to add modules from other Git " +"repositories into the branches of your repository. Adding these dependencies" +" in your branch through submodules makes the deployment of your code and " +"servers easier, as you can clone the repositories added as submodules at the" +" same time you clone your own repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:19 +msgid "" +"Besides, you can choose the branch of the repository added as submodule and " +"you have the control of the revision you want. It's up to you to decide " +"whether you want to pin the submodule to a specific revision and when you " +"want to update to a newer revision." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:24 +msgid "" +"In Odoo.sh, the submodules give you the possibility to use and depend on " +"modules available in other repositories. The platform will detect that you " +"added modules through submodules in your branches and add them to your " +"addons path automatically so you can install them in your databases." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:28 +msgid "" +"If you add private repositories as submodules in your branches, you need to " +"configure a deploy key in your Odoo.sh project settings and in your " +"repository settings. Otherwise Odoo.sh won't be allowed to download them. " +"The procedure is detailed in the chapter :ref:`Settings > Submodules " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:34 +msgid "Adding a submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:37 +msgid "With Odoo.sh (simple)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:40 +msgid "" +"For now it is not possible to add **private** repositories with this method." +" You can nevertheless do so :ref:`with Git `." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:43 +msgid "" +"On Odoo.sh, in the branches view of your project, choose the branch in which" +" you want to add a submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:45 +msgid "" +"In the upper right corner, click on the *Submodule* button, and then on " +"*Run*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:50 +msgid "A dialog with a form is shown. Fill the inputs as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:52 +msgid "Repository URL: The SSH URL of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:53 +msgid "Branch: The branch you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:54 +msgid "" +"Path: The folder in which you want to add this submodule in your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:59 +msgid "" +"On Github, you can get the repository URL with the *Clone or download* " +"button of the repository. Make sure to *use SSH*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:67 +msgid "With Git (advanced)" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:69 +msgid "" +"In a terminal, in the folder where your Git repository is cloned, checkout " +"the branch in which you want to add a submodule:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:76 +msgid "Then, add the submodule using the command below:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:82 +#: ../../content/administration/odoo_sh/advanced/submodules.rst:94 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:360 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:498 +msgid "Replace" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:84 +msgid "" +"*:* by the SSH URL of the " +"repository you want to add as submodule," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:85 +msgid "** by the branch you want to use in the above repository," +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:86 +msgid "** by the folder in which you want to add this submodule." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:88 +msgid "Commit and push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:96 +msgid "" +" by the repository on which you want to push your changes. For a " +"standard Git setup, this is *origin*." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:97 +msgid "" +" by the branch on which you want to push your changes. Most likely " +"the branch you used :code:`git checkout` on in the first step." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:100 +msgid "" +"You can read the `git-scm.com documentation `_ for more details about the Git " +"submodules. For instance, if you would like to update your submodules to " +"have their latest revision, you can follow the chapter `Pulling in Upstream " +"changes `_." +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:107 +msgid "Ignore modules" +msgstr "" + +#: ../../content/administration/odoo_sh/advanced/submodules.rst:109 +msgid "" +"If you're adding a repository that contains a lot of modules, you may want " +"to ignore some of them in case there are any that are installed " +"automatically. To do so, you can prefix your submodule folder with a " +":code:`.`. The platform will ignore this folder and you can hand pick your " +"modules by creating symlinks to them from another folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started.rst:5 +msgid "Get started" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:3 +msgid "Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:8 +msgid "" +"The branches view gives you an overview of the different branches your " +"repository has." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:16 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:41 +msgid "Stages" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:18 +msgid "" +"Odoo.sh offers three different stages for your branches: production, staging" +" and development." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:20 +msgid "" +"You can change the stage of a branch by drag and dropping it into the stage " +"section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:28 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:44 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:132 +msgid "Production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:30 +msgid "" +"This is the branch holding the code on which your production database runs. " +"There can be only one production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:33 +msgid "" +"When you push a new commit in this branch, your production server is updated" +" with the code of the new revision and is then restarted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:36 +msgid "" +"If your changes require the update of a module, such as a change in a form " +"view, and you want it to be performed automatically, increase the version " +"number of the module in its manifest (*__manifest__.py*). The platform will " +"then take care to perform the update during which the instance will be held " +"temporarily unavailable for maintenance reason." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:43 +msgid "" +"This method is equivalent to perform an upgrade of the module through the " +"Apps menu, or through the :code:`-u` switch of :doc:`the command line " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:47 +msgid "" +"In the case the changes in the commit prevent the server to restart, or if " +"the modules update fails, the server is automatically reverted to the " +"previous successful code revision and the database is roll-backed as it was " +"before the update. You still have access to the log of the failed update, so" +" you can troubleshoot it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:53 +msgid "" +"The demo data is not loaded, as it is not meant to be used in a production " +"database. The unit tests are not performed, as it would increase the " +"unavailability time of the production database during the updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:57 +msgid "" +"Partners using trial projects should be aware their production branch, along" +" with all the staging branches, will automatically be set back to the " +"development stage after 30 days." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:61 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:87 +msgid "Staging" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:63 +msgid "" +"Staging branches are meant to test your new features using the production " +"data without compromising the actual production database with test records. " +"They will create databases that are neutralized duplicates of the production" +" database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:67 +msgid "The neutralization includes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:69 +msgid "" +"Disabling scheduled actions. If you want to test them, you can trigger their" +" action manually or re-enable them. Be aware that the platform will trigger " +"them less often if no one is using the database in order to save up " +"resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:72 +msgid "" +"Disabling outgoing emails by intercepting them with a mailcatcher. An " +":ref:`interface to view ` the " +"emails sent by your database is provided. That way, you do not have to worry" +" about sending test emails to your contacts." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:75 +msgid "Setting payment providers and shipping providers in test mode." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:76 +msgid "Disabling IAP services" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:78 +msgid "" +"The latest database will be kept alive indefinitely, older ones from the " +"same branch may get garbage collected to make room for new ones. It will be " +"valid for 3 months, after which you will be expected to rebuild the branch. " +"If you make configuration or view changes in these databases, make sure to " +"document them or write them directly in the modules of the branch, using XML" +" data files overriding the default configuration or views." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:83 +msgid "" +"The unit tests are not performed as, in Odoo, they currently rely on the " +"demo data, which is not loaded in the production database. In the future, if" +" Odoo supports to run the unit tests without the demo data, Odoo.sh will " +"then consider running the tests on staging databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:88 +#: ../../content/administration/odoo_sh/getting_started/builds.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:57 +msgid "Development" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:90 +msgid "" +"Development branches create new databases using the demo data to run the " +"unit tests. The installed modules are the ones included in your branches. " +"You can change this list of modules to install in your :ref:`project " +"Settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:94 +msgid "" +"When you push a new commit in one of these branches, a new server is " +"started, with a database created from scratch and the new revision of the " +"branch. The demo data is loaded, and the unit tests are performed by " +"default. This verifies your changes do not break any of the features tested " +"by them. If you wish, you can disable the tests or allow specific tests to " +"be run with custom tags in the :ref:`branch's settings `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:101 +msgid "" +"Similar to staging branches, the emails are not sent but are intercepted by " +"a mailcatcher and scheduled actions are not triggered as long as the " +"database is not in use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:104 +msgid "" +"The databases created for development branches are meant to live around " +"three days. After that, they can be automatically garbage collected to make " +"room for new databases without prior notice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:110 +msgid "Merging your branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:112 +msgid "" +"You can merge your branches easily by drag and dropping them into each " +"other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:117 +msgid "" +"When you want to test the changes of your development branches with the " +"production data, you can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:120 +msgid "" +"merge the development branch into your staging branch, by drag and dropping " +"it onto the desired staging branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:121 +msgid "" +"drag and dropping the development branch on the staging section title, to " +"make it become a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:123 +msgid "" +"When your latest changes are ready for production, you can drag and drop " +"your staging branch onto your production branch to merge and deploy in " +"production your newest features." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:127 +msgid "" +"If you are bold enough, you can merge your development branches into your " +"production branch as well. It just means you skip the validation of your " +"changes with the production data through a staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:131 +msgid "" +"You can merge your development branches into each other, and your staging " +"branches into each other." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:133 +msgid "" +"Of course, you can also use :code:`git merge` directly on your workstation " +"to merge your branches. Odoo.sh will be notified when new revisions have " +"been pushed in your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:136 +msgid "" +"Merging a staging branch in the production branch only merges the source " +"code: Any configuration changes you made in the staging databases are not " +"passed to the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:139 +msgid "" +"If you test configuration changes in staging branches, and want them to be " +"applied in the production, you have to either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:141 +msgid "" +"write the configuration changes in XML data files overriding the default " +"configuration or views in your branches, and then increase the version of " +"your module in its manifest (*__manifest__.py*) to trigger the update of the" +" module when you merge your staging branch in your production branch. This " +"is the best practice for a better scalability of your developments as you " +"will use the Git versioning features for all your configuration changes, and" +" therefore have a traceability for your changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:147 +msgid "" +"pass them manually from your staging to your production database, by " +"copy/pasting them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:152 +msgid "Tabs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:155 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:58 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:88 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:133 +msgid "History" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:157 +msgid "An overview of your branch history:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:159 +msgid "The messages of the commits and their authors," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:160 +msgid "" +"The various events linked to the platform, such as stage changes, database " +"imports, backup restores." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:165 +msgid "" +"For each event, a status is displayed in the top right-hand corner. It can " +"provide information about the ongoing operation on the database " +"(installation, update, backup import, ...), or its result (tests feedback, " +"successful backup import, ...). When an operation is successful, you can " +"access the database thanks to the *connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:78 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:108 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:153 +msgid "Mails" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:175 +msgid "" +"This tab contains the mail catcher. It displays an overview of the emails " +"sent by your database. The mail catcher is available for your development " +"and staging branches as the emails of your production database are really " +"sent instead of being intercepted." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:184 +msgid "Shell" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:186 +msgid "" +"A shell access to your container. You can perform basic linux commands " +"(:code:`ls`, :code:`top`) and open a shell on your database by typing " +":code:`psql`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:192 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:208 +msgid "" +"You can open multiple tabs and drag-and-drop them to arrange the layout as " +"you wish, for instance side by side." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:196 +msgid "" +"Long running shell instances are not guaranteed. Idle shells can be " +"disconnected at anytime in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:200 +msgid "Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:202 +msgid "" +"An online integrated development environment (IDE) to edit the source code. " +"You can also open terminals, Python consoles and even Odoo Shell consoles." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:212 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:113 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:158 +msgid "Monitoring" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:214 +msgid "This link contains various monitoring metrics of the current build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:219 +msgid "" +"You can zoom, change the time range or select a specific metric on each " +"graph. On the graphs, annotations help you relate to changes on the build " +"(database import, git push, etc...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:225 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:68 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:98 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:143 +msgid "Logs" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:227 +msgid "A viewer to have a look to your server logs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:232 +msgid "Different logs are available:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:234 +msgid "" +"install.log: The logs of the database installation. In a development branch," +" the logs of the tests are included." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:235 +msgid "pip.log: The logs of the Python dependencies installation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:236 +msgid "odoo.log: The logs of the running server." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:237 +msgid "update.log: The logs of the database updates." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:238 +msgid "" +"pg_long_queries.log: The logs of psql queries that take an unusual amount of" +" time." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:240 +msgid "" +"If new lines are added in the logs, they will be displayed automatically. If" +" you scroll to the bottom, the browser will scroll automatically each time a" +" new line is added." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:243 +msgid "" +"You can pause the logs fetching by clicking on the according button in the " +"upper right corner of the view. The fetching is automatically stopped after " +"5 minutes. You can restart it using the play button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:249 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:118 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:163 +msgid "Backups" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:251 +msgid "" +"A list of the backups available for download and restore, the ability to " +"perform a manual backup and to import a database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:257 +msgid "" +"Odoo.sh makes daily backups of the production database. It keeps 7 daily, 4 " +"weekly and 3 monthly backups. Each backup includes the database dump, the " +"filestore (attachments, binary fields), logs and sessions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:260 +msgid "" +"Staging and development databases are not backed up. You nevertheless have " +"the possibility to restore a backup of the production database in your " +"staging branches, for testing purposes, or to manually recover data that has" +" been deleted by accident from the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:264 +msgid "" +"The list contains the backups kept on the server your production database is" +" hosted on. This server only keeps one month of backups: 7 daily and 4 " +"weekly backups." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:267 +msgid "" +"Dedicated backup servers keep the same backups, as well as 3 additional " +"monthly backups. To restore or download one of these monthly backups, please" +" `contact us `_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:270 +msgid "" +"If you merge a commit updating the version of one or several modules (in " +":file:`__manifest__.py`), or their linked python dependencies (in " +":file:`requirements.txt`), then Odoo.sh performs a backup automatically " +"(flagged with type Update in the list), as either the container will be " +"changed by the installation of new pip packages, either the database itself " +"will be changed with the module update triggered afterwards. In these two " +"cases, we are doing a backup as it may potentially break things." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:276 +msgid "" +"If you merge a commit that only changes some code without the above-" +"mentioned modifications, then no backup is done by Odoo.sh, as neither the " +"container nor the database is modified so the platform considers this safe " +"enough. Of course, as an extra precaution, you can make a backup manually " +"before making big changes in your production sources in case something goes " +"wrong (those manual backups are available for about one week). To avoid " +"abuse, we limit manual backups to 5 per day." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:282 +msgid "" +"The *import database* feature accepts database archives in the format " +"provided by:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:284 +msgid "" +"the standard Odoo databases manager, (available for on-premise Odoo servers " +"under :code:`/web/database/manager`)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:286 +msgid "the Odoo online databases manager," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:287 +msgid "the Odoo.sh backup download button of this *Backups* tab," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:288 +msgid "" +"the Odoo.sh dump download button in the :ref:`Builds view `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:295 +msgid "Available for production and staging branches for valid projects." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:298 +msgid ":doc:`Upgrade documentation <../../upgrade>`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:303 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:3 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:83 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:128 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:173 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:182 +msgid "Settings" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:305 +msgid "" +"Here you can find a couple of settings that only apply to the currently " +"selected branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:310 +msgid "**Behaviour upon new commit**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:312 +msgid "" +"For development and staging branches, you can change the branch's behavior " +"upon receiving a new commit. By default, a development branch will create a " +"new build and a staging branch will update the previous build (see the " +":ref:`Production Stage `). This is especially useful " +"should the feature you're working on require a particular setup or " +"configuration, to avoid having to manually set it up again on every commit. " +"If you choose new build for a staging branch, it will make a fresh copy from" +" the production build every time a commit is pushed. A branch that is put " +"back from staging to development will automatically be set to 'Do nothing'." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:320 +msgid "**Modules installation**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:322 +msgid "" +"Choose the modules to install automatically for your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:327 +msgid "" +"*Install only my modules* will install the modules of the branch only. This " +"is the default option. The :ref:`submodules ` " +"are excluded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:329 +msgid "" +"*Full installation (all modules)* will install the modules of the branch, " +"the modules included in the submodules and all standard modules of Odoo. " +"When running the full installation, the test suite is disabled." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:331 +msgid "" +"*Install a list of modules* will install the modules specified in the input " +"just below this option. The names are the technical name of the modules, and" +" they must be comma-separated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:334 +msgid "" +"If the tests are enabled, the standard Odoo modules suite can take up to 1 " +"hour. This setting applies to development builds only. Staging builds " +"duplicate the production build and the production build only installs base." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:339 +msgid "**Test suite**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:341 +msgid "" +"For development branches, you can choose to enable or disable the test " +"suite. It's enabled by default. When the test suite is enabled, you can " +"restrict them by specifying test tags :ref:`test tags " +"`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:345 +msgid "**Odoo Version**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:347 +msgid "" +"For development branches only, you can change the version of Odoo, should " +"you want to test upgraded code or develop features while your production " +"database is in the process of being upgraded to a newer version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:350 +msgid "" +"In addition, for each version you have two options regarding the code " +"update." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:352 +msgid "" +"You can choose to benefit from the latest bug, security and performance " +"fixes automatically. The sources of your Odoo server will be updated weekly." +" This is the 'Latest' option." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:354 +msgid "" +"You can choose to pin the Odoo sources to a specific revision by selecting " +"them from a list of dates. Revisions will expire after 3 months. You will be" +" notified by mail when the expiration date approaches and if you don't take " +"action afterwards, you will automatically be set to the latest revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:359 +msgid "**Custom domains**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:361 +msgid "" +"Here you can configure additional domains for the selected branch. It's " +"possible to add other *.odoo.com* domains or your own custom domains. " +"For the latter you have to:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:364 +msgid "own or purchase the domain name," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:365 +msgid "add the domain name in this list," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:366 +msgid "" +"in your registrar's domain name manager, configure the domain name with a " +"``CNAME`` record set to your production database domain name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:369 +msgid "" +"For instance, to associate *www.mycompany.com* to your database " +"*mycompany.odoo.com*:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:371 +msgid "" +"in Odoo.sh, add *www.mycompany.com* in the custom domains of your project " +"settings," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:372 +msgid "" +"in your domain name manager (e.g. *godaddy.com*, *gandi.net*, *ovh.com*), " +"configure *www.mycompany.com* with a ``CNAME`` record with as value " +"*mycompany.odoo.com*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:375 +msgid "Bare domains (e.g. *mycompany.com*) are not accepted:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:377 +msgid "they can only be configured using ``A`` records," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:378 +msgid "``A`` records only accept IP addresses as value," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:379 +msgid "" +"the IP address of your database can change, following an upgrade, a hardware" +" failure or your wish to host your database in another country or continent." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:382 +msgid "" +"Therefore, bare domains could suddenly no longer work because of this change" +" of IP address." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:384 +msgid "" +"In addition, if you would like both *mycompany.com* and *www.mycompany.com* " +"to work with your database, having the first redirecting to the second is " +"amongst the `SEO best practices " +"`_ (See *Provide" +" one version of a URL to reach a document*) in order to have one dominant " +"URL. You can therefore just configure *mycompany.com* to redirect to " +"*www.mycompany.com*. Most domain managers have the feature to configure this" +" redirection. This is commonly called a web redirection." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:391 +msgid "**HTTPS/SSL**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:393 +msgid "" +"If the redirection is correctly set up, the platform will automatically " +"generate an SSL certificate with `Let's Encrypt " +"`_ within the hour and your domain will be " +"accessible through HTTPS." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:397 +msgid "" +"While it is currently not possible to configure your own SSL certificates on" +" the Odoo.sh platform we are considering the feature if there is enough " +"demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:401 +msgid "**SPF and DKIM compliance**" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:403 +msgid "" +"In case the domain of your users email addresses use SPF (Sender Policy " +"Framework) or DKIM (DomainKeys Identified Mail), don't forget to authorize " +"Odoo as a sending host in your domain name settings to increase the " +"deliverability of your outgoing emails. The configuration steps are " +"explained in the documentation about :ref:`SPF ` and " +":ref:`DKIM `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:410 +msgid "" +"Forgetting to configure your SPF or DKIM to authorize Odoo as a sending host" +" can lead to the delivery of your emails as spam in your contacts inbox." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:414 +msgid "Shell commands" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:416 +msgid "" +"In the top right-hand corner of the view, different shell commands are " +"available." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:421 +msgid "" +"Each command can be copied in the clipboard to be used in a terminal, and " +"some of them can be used directly from Odoo.sh by clicking the *run* button " +"in such case a popup will prompt the user in order to define eventual " +"placeholders such as ````, ````, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:427 +msgid "Clone" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:429 +msgid "Download the Git repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:435 +msgid "Clones the repository *odoo/odoo*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:437 +msgid "" +":code:`--recurse-submodules`: Downloads the submodules of your repository. " +"Submodules included in the submodules are downloaded as well." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:438 +msgid "" +":code:`--branch`: checks out a specific branch of the repository, in this " +"case *master*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:440 +msgid "" +"The *run* button is not available for this command, as it is meant to be " +"used on your machines." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:443 +msgid "Fork" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:445 +msgid "Create a new branch based on the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:451 +msgid "" +"Creates a new branch called *feature-1* based on the branch *master*, and " +"then checkouts it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:457 +msgid "Uploads the new branch *feature-1* on your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:460 +msgid "Merge" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:462 +msgid "Merge the current branch in another branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:468 +msgid "Merges the branch *staging-1* in the current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:474 +#: ../../content/administration/odoo_sh/getting_started/branches.rst:547 +msgid "" +"Uploads the changes you just added in the *master* branch on your remote " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:477 +msgid "SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:480 +msgid "Setup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:482 +msgid "" +"In order to use SSH, you have to set up your profile SSH public key (if it " +"is not already done). To do so, follow these steps:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:485 +msgid "" +"`Generate a new SSH key `_" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:487 +msgid "" +"`Copy the SSH key to your clipboard " +"`_ (only apply the step 1)" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:490 +msgid "Paste the copied content to your profile SSH keys and press \"Add\"" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:495 +msgid "The key should appear below" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:501 +msgid "Connection" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:503 +msgid "" +"To connect to your builds using ssh use the following command in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:509 +msgid "" +"You will find a shortcut for this command into the SSH tab in the upper " +"right corner." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:514 +msgid "" +"Provided you have the :ref:`correct access rights ` on the project, you'll be granted ssh access to the" +" build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:518 +msgid "" +"Long running ssh connections are not guaranteed. Idle connections will be " +"disconnected in order to free up resources." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:522 +msgid "Submodule" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:524 +msgid "" +"Add a branch from another repository in your current branch as a " +"*submodule*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:526 +msgid "" +"*Submodules* allows you to use modules from other repositories in your " +"project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:528 +msgid "" +"The submodules feature is detailed in the chapter :ref:`Submodules ` of this documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:535 +msgid "" +"Adds the branch *master* of the repository ** as a submodule under the " +"path ** in your current branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:541 +msgid "Commits all your current changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:552 +msgid "Delete a branch from your repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:558 +msgid "Deletes the branch in your remote repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/branches.rst:564 +msgid "Deletes the branch in your local copy of the repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:6 +msgid "Builds" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:11 +msgid "" +"In Odoo.sh, a build is considered as a database loaded by an Odoo server " +"(`odoo/odoo `_ & `odoo/enterprise " +"`_) running on a specific revision of " +"your project repository in a containerized environment. Its purpose is to " +"test the well-behavior of the server, the database and the features with " +"this revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:20 +msgid "" +"In this view, a row represents a branch, and a cell of a row represents a " +"build of this branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:22 +msgid "" +"Most of the time, builds are created following pushes on your Github " +"repository branches. They can be created as well when you do other " +"operations, such as importing a database on Odoo.sh or asking a rebuild for " +"a branch in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:26 +msgid "" +"A build is considered successful if no errors or warnings come up during its" +" creation. A successful build is highlighted in green." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:29 +msgid "" +"A build is considered failed if errors come up during its creation. A failed" +" build is highlighted in red." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:32 +msgid "" +"If warnings come up during the creation, but there are no errors, the build " +"is considered almost successful. It is highlighted in yellow to notify the " +"developer warnings were raised." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:35 +msgid "" +"Builds do not always create a database from scratch. For instance, when " +"pushing a change on the production branch, the build created just starts the" +" server with your new revision and tries to load the current production " +"database on it. If no errors come up, the build is considered successful, " +"and otherwise failed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:46 +msgid "" +"The first build of a production branch creates a database from scratch. If " +"this build is successful, this database is considered as the production " +"database of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:49 +msgid "" +"From then, pushes on the production branch will create new builds that " +"attempt to load the database using a server running with the new revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:52 +msgid "" +"If the build is successful, or has warnings but no errors, the production " +"database will now run with this build, along with the revision associated to" +" this build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:55 +msgid "" +"If the build fails to load or update the database, then the previous " +"successful build is re-used to load the database, and therefore the database" +" will run using a server running with the previous successful revision." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:59 +msgid "" +"The build used to run the production database is always the first of the " +"builds list. If a build fails, it is put after the build currently running " +"the production database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:65 +msgid "" +"Staging builds duplicate the production database, and try to load this " +"duplicate with the revisions of the staging branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:68 +msgid "" +"Each time you push a new revision on a staging branch, the build created " +"uses a new copy of the production database. The databases are not re-used " +"between builds of the same branch. This ensures:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:71 +msgid "" +"staging builds use databases that are close to what the production looks " +"like, so you do not make your tests with outdated data," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:74 +msgid "" +"you can play around as much as you want in the same staging database, and " +"you can then ask for a rebuild when you want to restart with a new copy of " +"the production." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:77 +msgid "" +"Nevertheless, this means that if you make configuration changes in staging " +"databases and do not apply them in the production, they will not be passed " +"on the next build of the same staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:83 +msgid "" +"Development builds create new databases, load the demo data and run the unit" +" tests." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:85 +msgid "" +"A build will be considered failed and highlighted in red if tests fail " +"during the installation, as they are meant to raise errors if something " +"wrong occurs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:88 +msgid "" +"If all tests pass, and there is no error, the build will be considered " +"successful." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:90 +msgid "" +"According to the list of modules to install and test, a development build " +"can take up to 1 hour to be ready. This is due to the large number of tests " +"set in the default Odoo modules suite." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:94 +msgid "Features" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:96 +msgid "" +"The production branch will always appear first, and then the other branches " +"are ordered by last build created. You can filter out the branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:102 +msgid "" +"For each branch, you can access the last build's database using the " +"*Connect* link and jump to the branch code using the *Github* link. For " +"other branches than the production, you can create a new build which will " +"use the latest revision of the branch using the link *rebuild*. This last " +"link is not available when there is already a build in progress for the " +"branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:110 +msgid "" +"For each build, you can access the revision changes using the button with " +"the Github icon. You can access the build's database as the administrator " +"using the *Connect* button. Also, you can access the database with another " +"user using the *Connect as* button, in the dropdown menu of the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/builds.rst:122 +msgid "" +"In the dropdown menu of the build, you can access the same features than in " +":ref:`the branches view `: *Logs*, *Web" +" Shell*, *Editor*, *Outgoing e-mails*. You also have the possibility to " +"*Download a dump* of the build's database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:6 +msgid "Create your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:9 +msgid "Deploy your platform" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:11 +msgid "" +"Go to `Odoo.sh `_ and hit the *Deploy your platform* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:17 +msgid "Sign in with Github" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:19 +msgid "" +"Sign in with your Github account. If you do not have an account yet, hit the" +" *Create an account* link." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:26 +msgid "Authorize Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:28 +msgid "" +"Grant Odoo.sh the required accesses to your account by clicking the " +"*Authorize* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:33 +msgid "Odoo.sh basically needs:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:35 +msgid "to know your Github login and email," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:36 +msgid "to create a new repository in case you decide to start from scratch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:37 +msgid "" +"to read your existing repositories, including the ones of your " +"organizations, in case you want to start from an existing repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:39 +msgid "to create a webhook to be notified each time you push changes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:40 +msgid "" +"to commit changes to make your deployment easier, merging branches or adding" +" new `submodules `_ for" +" example." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:44 +msgid "Submit your project" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:46 +msgid "" +"Choose if you want to start from scratch by creating a new repository, or if" +" you want to use an existing repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:49 +msgid "Then, choose a name or select the repository you want to use." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:51 +msgid "" +"Choose the Odoo version you want to use. If you plan to import an existing " +"database or an existing set of applications, you might need to choose the " +"according version. If you start from scratch, use the latest version." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:55 +msgid "" +"Enter your *subscription code*. This is also called *subscription referral*," +" *contract number* or *activation code*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:58 +msgid "" +"It should be the code of your Enterprise subscription that includes Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:60 +msgid "" +"Partners can use their partnership codes to start a trial. Should their " +"clients start a project, they ought to get an Enterprise subscription " +"including Odoo.sh and use its subscription code. The partner will get 50% of" +" the amount back as commission. Contact your sales representative or account" +" manager in order to get it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:65 +msgid "" +"When submitting the form, if you are notified your subscription is not " +"valid, it either means:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:67 +msgid "it is not an existing subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:68 +msgid "it is not a partnership subscription," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:69 +msgid "it is an enterprise subscription, but which does not include Odoo.sh," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:70 +msgid "" +"it is neither a partnership subscription or an enterprise subscription (e.g." +" an online subscription)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:73 +msgid "" +"In case of doubt with your subscription, please contact the `Odoo support " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:80 +msgid "You're done !" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:82 +msgid "" +"You can start using Odoo.sh. Your first build is about to be created. You " +"will soon be able to connect to your first database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:91 +msgid "Import your database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:93 +msgid "" +"You can import your database in your Odoo.sh project as long as it is in a " +":doc:`supported version ` of Odoo." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:97 +msgid "Push your modules in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:99 +msgid "" +"If you use community or custom modules, add them in a branch in your Github " +"repository. Databases hosted on the Odoo.com online platform do not have any" +" custom modules. Users of these databases can therefore skip this step." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:103 +msgid "" +"You can structure your modules as you wish, Odoo.sh will automatically " +"detect the folders containing Odoo addons. For instance, you can put all " +"your modules folder in the root directory of your repository, or group the " +"modules in folders by categories that you define (accounting, project, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:108 +msgid "" +"For community modules available in public Git repositories, you can also " +"consider to add them using :ref:`Submodules `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:111 +msgid "" +"Then, either :ref:`make this branch the production branch `, or :ref:`merge it into your production " +"branch `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:115 +msgid "Download a backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:118 +msgid "On-premise databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:120 +msgid "" +"Access the URL :file:`/web/database/manager` of your on-premise database and" +" download a backup." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:124 +msgid "" +"If you cannot access the database manager, it may have been disabled by your" +" system administrator. See the :ref:`database manager security documentation" +" `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:127 +msgid "" +"You will need the master password of your database server. If you do not " +"have it, contact your system administrator." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:133 +msgid "Choose a zip including the filestore as the backup format." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:139 +msgid "Odoo Online databases" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:141 +msgid "" +"`Access your databases manager " +"`_ and download a backup of " +"your database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:149 +msgid "Online versions (e.g. *saas-**) are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:152 +msgid "Upload the backup" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:154 +msgid "" +"Then, in your Odoo.sh project, in the backups tab of your production branch," +" import the backup you just downloaded." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:160 +msgid "" +"Once the backup imported, you can access the database using the *Connect* " +"button in the history of the branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:167 +msgid "Check your outgoing email servers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:169 +msgid "" +"There is a default mail server provided with Odoo.sh. To use it, there must " +"be no enabled outgoing mail server configured in your database in " +":menuselection:`Settings --> Technical --> Outgoing Mail Servers` " +"(:ref:`Developer mode ` must be activated)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:174 +msgid "" +"After the import of your database, all outgoing email servers are disabled " +"so you use the Odoo.sh email server provided by default." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:178 +msgid "" +"Port 25 is (and will stay) closed. If you want to connect to an external " +"SMTP server, you should use ports 465 and 587." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:182 +msgid "Check your scheduled actions" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:184 +msgid "All scheduled actions are disabled after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:186 +msgid "" +"This is to prevent your newly imported database to perform actions that " +"could impact your running production, such as sending the mails remaining in" +" the queue, processing mass mailings, or third-party services " +"synchronization (Calendars, files hosting, ...)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:190 +msgid "" +"If you plan to make the imported database your production, enable the " +"scheduled actions you need. You can check what is enabled in the database of" +" origin and enable the same actions in the imported database. Scheduled " +"actions are located under :menuselection:`Settings --> Technical --> " +"Automation --> Scheduled Actions`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:196 +msgid "Register your subscription" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:198 +msgid "Your subscription is unlinked after the import." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:200 +msgid "" +"The imported database is considered a duplicate by default and the " +"enterprise subscription is therefore removed, as you can only have one " +"database linked per subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/create.rst:203 +msgid "" +"If you plan to make it your production, unlink your former database from the" +" subscription, and register the newly imported database. Read the " +":doc:`database registration documentation <../../on_premise>` for " +"instructions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:3 +msgid "Your first module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:8 +msgid "" +"This chapter helps you to create your first Odoo module and deploy it in " +"your Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:10 +msgid "" +"This tutorial requires :ref:`you created a project on Odoo.sh `, and you know your Github repository's URL." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:13 +msgid "Basic use of Git and Github is explained." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:15 +msgid "The below assumptions are made:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:17 +msgid "" +"*~/src* is the directory where are located the Git repositories related to " +"your Odoo projects," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:18 +msgid "*odoo* is the Github user," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:19 +msgid "*odoo-addons* is the Github repository," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:20 +msgid "*feature-1* is the name of a development branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:21 +msgid "*master* is the name of the production branch," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:22 +msgid "*my_module* is the name of the module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:24 +msgid "Replace these by the values of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:27 +msgid "Create the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:30 +msgid "From Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:32 +msgid "In the branches view:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:34 +msgid "hit the :code:`+` button next to the development stage," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:35 +msgid "choose the branch *master* in the *Fork* selection," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:36 +msgid "type *feature-1* in the *To* input." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:38 +msgid "|pic1| |pic2|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:40 +msgid "pic1" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:43 +msgid "pic2" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:46 +msgid "" +"Once the build created, you can access the editor and browse to the folder " +"*~/src/user* to access to the code of your development branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:56 +msgid "From your computer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:58 +msgid "Clone your Github repository on your computer:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:67 +msgid "Create a new branch:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:74 +msgid "Create the module structure" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:77 +msgid "Scaffolding the module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:79 +msgid "" +"While not necessary, scaffolding avoids the tedium of setting the basic Odoo" +" module structure. You can scaffold a new module using the executable *odoo-" +"bin*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:82 +msgid "From the Odoo.sh editor, in a terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:88 +msgid "" +"Or, from your computer, if you have an :doc:`installation of Odoo " +"<../../on_premise/source>`:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:94 +msgid "" +"If you do not want to bother installing Odoo on your computer, you can also " +":download:`download this module structure template " +"` in which you replace every occurrences of " +"*my_module* to the name of your choice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:98 +msgid "The below structure will be generated:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:121 +msgid "" +"Do not use special characters other than the underscore ( _ ) for your " +"module name, not even an hyphen ( - ). This name is used for the Python " +"classes of your module, and having classes name with special characters " +"other than the underscore is not valid in Python." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:125 +msgid "Uncomment the content of the files:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:127 +msgid "*models/models.py*, an example of model with its fields," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:129 +msgid "" +"*views/views.xml*, a tree and a form view, with the menus opening them," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:131 +msgid "*demo/demo.xml*, demo records for the above example model," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:133 +msgid "" +"*controllers/controllers.py*, an example of controller implementing some " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:135 +msgid "" +"*views/templates.xml*, two example qweb views used by the above controller " +"routes," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:137 +msgid "" +"*__manifest__.py*, the manifest of your module, including for instance its " +"title, description and data files to load. You just need to uncomment the " +"access control list data file:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:146 +msgid "Manually" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:148 +msgid "" +"If you want to create your module structure manually, you can follow the " +":doc:`/developer/tutorials/server_framework_101` tutorial to understand the " +"structure of a module and the content of each file." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:153 +msgid "Push the development branch" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:155 +msgid "Stage the changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:161 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:395 +msgid "Commit your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:167 +msgid "Push your changes to your remote repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:169 +msgid "From an Odoo.sh editor terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:175 +msgid "" +"The above command is explained in the section :ref:`Commit & Push your " +"changes ` of the :ref:`Online " +"Editor ` chapter. It includes the " +"explanation regarding the fact you will be prompted to type your username " +"and password, and what to do if you use the two-factor authentication." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:183 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:383 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:409 +msgid "Or, from your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:189 +msgid "" +"You need to specify *-u origin feature-1* for the first push only. From that" +" point, to push your future changes from your computer, you can simply use" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:197 +msgid "Test your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:199 +msgid "" +"Your branch should appear in your development branches in your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:204 +msgid "" +"In the branches view of your project, you can click on your branch name in " +"the left navigation panel to access its history." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:210 +msgid "" +"You can see here the changes you just pushed, including the comment you set." +" Once the database ready, you can access it by clicking the *Connect* " +"button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:216 +msgid "" +"If your Odoo.sh project is configured to install your module automatically, " +"you will directly see it amongst the database apps. Otherwise, it will be " +"available in the apps to install." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:220 +msgid "" +"You can then play around with your module, create new records and test your " +"features and buttons." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:223 +msgid "Test with the production data" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:225 +msgid "" +"You need to have a production database for this step. You can create it if " +"you do not have it yet." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:227 +msgid "" +"Once you tested your module in a development build with the demo data and " +"believe it is ready, you can test it with the production data using a " +"staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:230 +msgid "You can either:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:232 +msgid "" +"Make your development branch a staging branch, by drag and dropping it onto " +"the *staging* section title." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:238 +msgid "" +"Merge it in an existing staging branch, by drag and dropping it onto the " +"given staging branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:243 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:289 +msgid "You can also use the :code:`git merge` command to merge your branches." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:245 +msgid "" +"This will create a new staging build, which will duplicate the production " +"database and make it run using a server updated with your latest changes of " +"your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:251 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:297 +msgid "Once the database ready, you can access it using the *Connect* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:256 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:300 +msgid "Install your module" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:258 +msgid "" +"Your module will not be installed automatically, you have to install it from" +" the apps menu. Indeed, the purpose of the staging build is to test the " +"behavior of your changes as it would be on your production, and on your " +"production you would not like your module to be installed automatically, but" +" on demand." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:263 +msgid "" +"Your module may not appear directly in your apps to install either, you need" +" to update your apps list first:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:266 +msgid "Activate the :ref:`developer mode `" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:267 +msgid "in the apps menu, click the *Update Apps List* button," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:268 +msgid "in the dialog that appears, click the *Update* button." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:273 +msgid "Your module will then appear in the list of available apps." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:279 +msgid "Deploy in production" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:281 +msgid "" +"Once you tested your module in a staging branch with your production data, " +"and believe it is ready for production, you can merge your branch in the " +"production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:284 +msgid "Drag and drop your staging branch on the production branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:291 +msgid "" +"This will merge the latest changes of your staging branch in the production " +"branch, and update your production server with these latest changes." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:302 +msgid "" +"Your module will not be installed automatically, you have to install it " +"manually as explained in the :ref:`above section about installing your " +"module in staging databases `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:308 +msgid "Add a change" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:310 +msgid "" +"This section explains how to add a change in your module by adding a new " +"field in a model and deploy it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "From the Odoo.sh editor," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:314 +msgid "browse to your module folder *~/src/user/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:315 +msgid "then, open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:321 +msgid "Or, from your computer," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:318 +msgid "" +"use the file browser of your choice to browse to your module folder " +"*~/src/odoo-addons/my_module*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:320 +msgid "" +"then, open the file *models/models.py* using the editor of your choice, such" +" as *Atom*, *Sublime Text*, *PyCharm*, *vim*, ..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:323 +msgid "Then, after the description field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:329 +msgid "Add a datetime field" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:335 +msgid "Then, open the file *views/views.xml*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:337 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:473 +msgid "After" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:343 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:450 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:467 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:479 +msgid "Add" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:349 +msgid "" +"These changes alter the database structure by adding a column in a table, " +"and modify a view stored in database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:352 +msgid "" +"In order to be applied in existing databases, such as your production " +"database, these changes requires the module to be updated." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:355 +msgid "" +"If you would like the update to be performed automatically by the Odoo.sh " +"platform when you push your changes, increase your module version in its " +"manifest." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:358 +msgid "Open the module manifest *__manifest__.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:366 +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:504 +msgid "with" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:372 +msgid "" +"The platform will detect the change of version and trigger the update of the" +" module upon the new revision deployment." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:375 +msgid "Browse to your Git folder." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:377 +msgid "Then, from an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:389 +msgid "Then, stage your changes to be committed" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:401 +msgid "Push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:403 +msgid "From an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:415 +msgid "The platform will then create a new build for the branch *feature-1*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:420 +msgid "" +"Once you tested your changes, you can merge your changes in the production " +"branch, for instance by drag-and-dropping the branch on the production " +"branch in the Odoo.sh interface. As you increased the module version in the " +"manifest, the platform will update the module automatically and your new " +"field will be directly available. Otherwise you can manually update the " +"module within the apps list." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:426 +msgid "Use an external Python library" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:428 +msgid "" +"If you would like to use an external Python library which is not installed " +"by default, you can define a *requirements.txt* file listing the external " +"libraries your modules depends on." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:432 +msgid "" +"It is not possible to install or upgrade system packages on an Odoo.sh " +"database (e.g., apt packages). However, under specific conditions, packages " +"can be considered for installation. This also applies to **Python modules** " +"requiring system packages for their compilation, and **third-party Odoo " +"modules**." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:436 +msgid "**PostgreSQL extensions** are not supported on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:437 +msgid "" +"For more information, consult our `FAQ " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:439 +msgid "" +"The platform will use this file to automatically install the Python " +"libraries your project needs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:441 +msgid "" +"The feature is explained in this section by using the `Unidecode library " +"`_ in your module." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:444 +msgid "Create a file *requirements.txt* in the root folder of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:446 +msgid "" +"From the Odoo.sh editor, create and open the file " +"~/src/user/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:448 +msgid "" +"Or, from your computer, create and open the file ~/src/odoo-" +"addons/requirements.txt." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:456 +msgid "" +"Then use the library in your module, for instance to remove accents from " +"characters in the name field of your model." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:459 +msgid "Open the file *models/models.py*." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:461 +msgid "Before" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:494 +msgid "" +"Adding a Python dependency requires a module version increase for the " +"platform to install it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:496 +msgid "Edit the module manifest *__manifest__.py*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:510 +msgid "Stage and commit your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:518 +msgid "Then, push your changes:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:520 +msgid "In an Odoo.sh terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/first_module.rst:526 +msgid "In your computer terminal:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:6 +msgid "Online Editor" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:11 +msgid "" +"The online editor allows you to edit the source code of your builds from a " +"web browser. It also gives you the possibility to open terminals, Python " +"consoles, Odoo Shell consoles and `Notebooks " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:18 +msgid "" +"You can access the editor of a build through :ref:`the branches tabs " +"`, :ref:`the builds dropdown menu " +"` or by adding */odoo-sh/editor*" +" to your build domain name (e.g. *https://odoo-addons-" +"master-1.dev.odoo.com/odoo-sh/editor*)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:25 +msgid "Edit the source code" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:27 +msgid "The working directory is composed of the following folders:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:49 +msgid "" +"You can edit the source code (files under */src*) in development and staging" +" builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:52 +msgid "" +"Your changes won't be propagated to a new build, you must commit them in " +"your source code if you want to make them persist." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:56 +msgid "" +"For production builds, the source code is read-only, because applying local " +"changes on a production server is not a good practice." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:59 +msgid "" +"The source code of your Github repository is located under */src/user*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:60 +msgid "The source code of Odoo is located under" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:62 +msgid "*/src/odoo* (`odoo/odoo `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:63 +msgid "" +"*/src/enterprise* (`odoo/enterprise `_)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:64 +msgid "" +"*/src/themes* (`odoo/design-themes `_)." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:66 +msgid "" +"To open a file in the editor, just double-click on it in the file browser " +"panel on the left." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:71 +msgid "" +"You can then begin to make your changes. You can save your changes with the " +"menu :menuselection:`File --> Save .. File` or by hitting the :kbd:`Ctrl+S` " +"shortcut." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:77 +msgid "" +"If you save a Python file which is under your Odoo server addons path, Odoo " +"will detect it and reload automatically so your changes are reflected " +"immediately, without having to restart the server manually." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:84 +msgid "" +"However, if the change is a data stored in database, such as the label of a " +"field, or a view, you have to update the according module to apply the " +"change. You can update the module of the currently opened file by using the " +"menu :menuselection:`Odoo --> Update current module`. Note that the file " +"considered as currently opened is the file focused in the text editor, not " +"the file highlighted in the file browser." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:93 +msgid "You can also open a terminal and execute the command:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:102 +msgid "Commit & Push your changes" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:104 +msgid "" +"You have the possibility to commit and push your changes to your Github " +"repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:106 +msgid "Open a terminal (:menuselection:`File --> New --> Terminal`)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:107 +msgid "Change the directory to *~/src/user* using :code:`cd ~/src/user`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:108 +msgid "Stage your changes using :code:`git add`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:109 +msgid "Commit your changes using :code:`git commit`," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:110 +msgid "Push your changes using :code:`git push https HEAD:`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:112 +msgid "In this last command," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:114 +msgid "" +"*https* is the name of your *HTTPS* Github remote repository (e.g. " +"https://github.com/username/repository.git)," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:116 +msgid "HEAD is the reference to the latest revision you committed," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:117 +msgid "" +" must be replaced by the name of the branch to which you want to " +"push the changes, most-likely the current branch if you work in a " +"development build." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:124 +msgid "" +"The SSH Github remote is not used because your SSH private key is not hosted" +" in your build containers (for obvious security concerns) nor forwarded " +"through an SSH Agent (as you access this editor through a web browser) and " +"you therefore cannot authenticate yourself to Github using SSH. You have to " +"use the HTTPS remote of your Github repository to push your changes, which " +"is added automatically named as *https* in your Git remotes. You will be " +"prompted to enter your Github username and password. If you activated the " +"two-factor authentication on Github, you can create a `personal access token" +" `_ and use it as password. Granting the ``repo`` permission " +"suffices." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:137 +msgid "" +"The Git source folder *~/src/user* is not checked out on a branch but rather" +" on a detached revision: This is because builds work on specific revisions " +"rather than branches. In other words, this means you can have multiple " +"builds on the same branch, but on different revisions." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:141 +msgid "" +"Once your changes are pushed, according to your :ref:`branch push behavior " +"`, a new build may be created." +" You can continue to work in the editor you pushed from, as it will have the" +" same revision as the new build that was created, but always make sure to be" +" in an editor of a build using the latest revision of your branch." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:148 +msgid "Consoles" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:150 +msgid "" +"You can open Python consoles, which are `IPython interactive shells " +"`_. One " +"of the most interesting addition to use a Python console rather than a " +"IPython shell within a terminal is the `rich display " +"`_ capabilities. Thanks to this, you will be able to display objects" +" in HTML." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:158 +msgid "" +"You can for instance display cells of a CSV file using `pandas " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:164 +msgid "" +"You can also open an Odoo Shell console to play around with the Odoo " +"registry and model methods of your database. You can also directly read or " +"write on your records." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:169 +msgid "" +"In an Odoo Console, transactions are automatically committed. This means, " +"for instance, that changes in records are applied effectively in the " +"database. If you change the name of a user, the name of the user is changed " +"in your database as well. You therefore should use Odoo consoles carefully " +"on production databases." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:174 +msgid "" +"You can use *env* to invoke models of your database registry, e.g. " +":code:`env['res.users']`." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:184 +msgid "" +"The class :code:`Pretty` gives you the possibility to easily display lists " +"and dicts in a pretty way, using the `rich display " +"`_ mentioned above." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/online-editor.rst:192 +msgid "" +"You can also use `pandas `_ to display graphs." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:8 +msgid "The settings allow you to manage the configuration of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:14 +msgid "Project name" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:16 +msgid "The name of your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:21 +msgid "" +"This defines the address that will be used to access your production " +"database." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:23 +msgid "" +"Addresses of your staging and development builds are derived from this name " +"and assigned automatically. However, when you change your project name, only" +" future builds will use the new name." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:29 +msgid "Collaborators" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:31 +msgid "Manage the Github users who can access your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:36 +msgid "There are three levels of users:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:38 +msgid ":guilabel:`Admin`: has access to all features of an Odoo.sh project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:40 +msgid "" +":guilabel:`Tester`: has access to the *Staging* and *Development* databases " +"and their tooling. This role is for users conducting User Acceptance Tests. " +"Testers can work with copies of production data but cannot access the " +"production database through the Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:44 +msgid "" +":guilabel:`Developer`: has access only to the *Development* databases and " +"their tooling. This role is for developers who propose code modifications " +"but are not allowed to access production and staging databases through the " +"Odoo.sh tooling." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:54 +msgid "Developer" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:55 +msgid "Tester" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:56 +msgid "Admin" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:59 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:60 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:61 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:64 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:65 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:66 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:69 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:70 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:71 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:74 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:75 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:76 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:79 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:80 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:81 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:84 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:85 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:86 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:89 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:90 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:91 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:95 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:96 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:100 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:101 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:105 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:106 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:110 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:111 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:115 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:116 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:121 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:125 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:126 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:130 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:131 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:134 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:135 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:136 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:141 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:146 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:151 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:156 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:161 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:166 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:171 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:176 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:179 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:180 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:181 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:186 +#: ../../content/administration/supported_versions.rst:35 +#: ../../content/administration/supported_versions.rst:41 +#: ../../content/administration/supported_versions.rst:47 +#: ../../content/administration/supported_versions.rst:53 +#: ../../content/administration/supported_versions.rst:59 +#: ../../content/administration/supported_versions.rst:60 +#: ../../content/administration/supported_versions.rst:61 +#: ../../content/administration/supported_versions.rst:77 +#: ../../content/administration/supported_versions.rst:78 +#: ../../content/administration/supported_versions.rst:79 +#: ../../content/administration/supported_versions.rst:83 +#: ../../content/administration/supported_versions.rst:84 +#: ../../content/administration/supported_versions.rst:85 +msgid "|green|" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:63 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:93 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:138 +msgid "1-click connect" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:73 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:103 +#: ../../content/administration/odoo_sh/getting_started/settings.rst:148 +msgid "Shell/SSH" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:177 +#: ../../content/administration/odoo_sh/getting_started/status.rst:3 +msgid "Status" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:189 +msgid "" +"Those roles only apply to the usage of Odoo.sh. It is important to reflect " +"the user roles attribution within the repository on GitHub. Please refer to" +" the GitHub documentation section on `Managing a branch protection rule " +"`_ for detailed guidance." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:207 +msgid "Public Access" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:209 +msgid "Allow public access to your development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:214 +msgid "" +"If activated, this option exposes the Builds page publicly, allowing " +"visitors to view logs of development builds." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:216 +msgid "" +"Production and staging builds are excluded, visitors can only see their " +"status." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:221 +msgid "GitHub commit statuses" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:223 +msgid "" +"This option enables Odoo.sh to push commit statuses to your GitHub " +"repository when a build is created or updated. It requires a GitHub token " +"with permissions to push commit statuses to the repository. Refer to " +"`GitHub's documentation on personal access tokens " +"`_ for instructions to create " +"yours." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:229 +msgid "" +"GitHub's **fine-grained personal tokens** have an expiration date and will " +"be disabled if they fail to update the commit status. You can replace the " +"token at any time on Odoo.sh." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:232 +msgid "The commit statuses pushed to GitHub can have the following contexts:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:234 +msgid ":guilabel:`ci/odoo.sh (dev)`: status of a development build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:235 +msgid ":guilabel:`ci/odoo.sh (staging)`: status of a staging build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:236 +msgid ":guilabel:`ci/odoo.sh (production)`: status of a production build" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:237 +msgid "" +":guilabel:`ci/odoo.sh (test_ci)`: testing the token from the Settings page " +"will push a test status on the last commit of your repository" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:241 +msgid "Custom domains" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:243 +msgid "" +"To configure additional domains please refer to the corresponding branch's " +":ref:`settings tab `." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:251 +msgid "" +"Configure the deploy keys for the private repositories you use as submodules" +" in your branches to allow Odoo.sh to download them." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:255 +msgid "" +"These settings are required for **private repositories** only. If you are " +"looking on how to set up your submodules, instructions are available in the " +"chapter :ref:`Submodules ` of this " +"documentation." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:262 +msgid "" +"When a repository is private, it is not possible to publicly download its " +"branches and revisions. For that reason, you need to configure a deploy key " +"for Odoo.sh, so the remote Git server allows our platform to download the " +"revisions of this private repository." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:267 +msgid "" +"To configure the deploy key for a private repository, proceed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:269 +msgid "" +"in the input, paste the SSH URL of your private sub-repository and click on " +"*Add*," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:271 +msgid "e.g. *git@github.com:USERNAME/REPOSITORY.git*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:272 +msgid "" +"it can be another Git server than Github, such as Bitbucket, Gitlab or even " +"your own self-hosted server" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:275 +msgid "copy the public key," +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:277 +msgid "it should look like *ssh-rsa some...random...characters...here...==*" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:279 +msgid "" +"in the settings of the private sub-repository, add the public key amongst " +"the deploy keys." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:281 +msgid "" +"Github.com: :menuselection:`Settings --> Deploy keys --> Add deploy key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:282 +msgid "Bitbucket.com: :menuselection:`Settings --> Access keys --> Add key`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:283 +msgid "Gitlab.com: :menuselection:`Settings --> Repository --> Deploy Keys`" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:284 +msgid "" +"Self-hosted: append the key to the git user’s authorized_keys file in its " +".ssh directory" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:287 +msgid "Storage Size" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:289 +msgid "This section shows the storage size used by your project." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:294 +msgid "Storage size is computed as follows:" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:296 +msgid "the size of the PostgreSQL database" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:298 +msgid "" +"the size of the disk files available in your container: database filestore, " +"sessions storage directory..." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:301 +msgid "" +"In case you want to analyze disk usage, you can run the tool `ncdu " +"`_ in your Web Shell." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:304 +msgid "" +"Should your production database size grow to exceed what's provisioned in " +"your subscription, it will automatically be synchronized with it." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:308 +msgid "Database Workers" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:310 +msgid "" +"Additional database workers can be configured here. More workers help " +"increase the load your production database is able to handle. If you add " +"more, it will automatically be synchronized with your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:318 +msgid "" +"Adding more workers will not magically solve all performance issues. It only" +" allows the server to handle more connections at the same time. If some " +"operations are unusually slow, it's most likely a problem with the code, if " +"it's not due to your own customizations you can open a ticket `here " +"`_." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:324 +msgid "Staging Branches" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:326 +msgid "" +"Additional staging branches allow you to develop and test more features at " +"the same time. If you add more, it will automatically be synchronized with " +"your subscription." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:333 +msgid "Activation" +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/settings.rst:335 +msgid "" +"Shows the status of the project's activation. You can change the project's " +"activation code if needed." +msgstr "" + +#: ../../content/administration/odoo_sh/getting_started/status.rst:8 +msgid "" +"The status page shows statistics regarding the servers your project uses. It" +" includes the servers availability." +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:3 +msgid "Introduction to Odoo.sh" +msgstr "" + +#: ../../content/administration/odoo_sh/overview/introduction.rst:10 +msgid "" +"The documentation will help you go live with your Odoo.sh project in no " +"time." +msgstr "" + +#: ../../content/administration/on_premise.rst:5 +#: ../../content/administration/upgrade.rst:30 +#: ../../content/administration/upgrade.rst:163 +#: ../../content/administration/upgrade.rst:371 +msgid "On-premise" +msgstr "" + +#: ../../content/administration/on_premise.rst:8 +msgid "Register a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:10 +msgid "" +"To register your database, enter your subscription code in the banner in the" +" app dashboard. If the registration is successful, the banner will turn " +"green and display the database expiration date." +msgstr "" + +#: ../../content/administration/on_premise.rst:14 +msgid "" +"The expiration date is also displayed at the bottom of the Settings page." +msgstr "" + +#: ../../content/administration/on_premise.rst:19 +msgid "Duplicate a database" +msgstr "" + +#: ../../content/administration/on_premise.rst:21 +msgid "" +"Duplicate a database by accessing the database manager on your server " +"(`/web/database/manager`). Typically, you want to duplicate " +"your production database into a neutralized testing database. It can be done" +" by checking the neutralize box when prompted, which executes all " +":file:`neutralize.sql` scripts for every installed module." +msgstr "" + +#: ../../content/administration/on_premise.rst:27 +msgid "Common error messages and solutions" +msgstr "" + +#: ../../content/administration/on_premise.rst:30 +msgid "Registration error" +msgstr "" + +#: ../../content/administration/on_premise.rst:32 +msgid "" +"In case of a registration error, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database registration error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:37 +msgid "To resolve the issue:" +msgstr "" + +#: ../../content/administration/on_premise.rst:39 +msgid "" +"Check the **validity of your Odoo Enterprise subscription** by verifying if " +"your subscription details have the tag :guilabel:`In Progress` on your `Odoo" +" Account `_ or contact your " +"Account Manager." +msgstr "" + +#: ../../content/administration/on_premise.rst:43 +msgid "" +"Ensure that **no other database is linked** to the subscription code, as " +"only one database can be linked per subscription." +msgstr "" + +#: ../../content/administration/on_premise.rst:47 +msgid "" +"If a test or a development database is needed, you can :ref:`duplicate a " +"database `." +msgstr "" + +#: ../../content/administration/on_premise.rst:50 +msgid "" +"Verify that **no databases share the same UUID** (Universally Unique " +"Identifier) by opening your `Odoo Contract " +"`_. If two or more databases " +"share the same UUID, their name will be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database UUID error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:57 +msgid "" +"If that is the case, manually change the database(s) UUID or `send a support" +" ticket `_." +msgstr "" + +#: ../../content/administration/on_premise.rst:60 +msgid "" +"As the update notification must be able to reach Odoo's subscription " +"validation servers, ensure your **network and firewall settings** allow the " +"Odoo server to open outgoing connections towards:" +msgstr "" + +#: ../../content/administration/on_premise.rst:64 +msgid "Odoo 18.0 and above: `services.odoo.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:65 +msgid "Odoo 17.0 and below: `services.openerp.com` on port `80`" +msgstr "" + +#: ../../content/administration/on_premise.rst:67 +msgid "" +"These ports must be kept open even after registering a database, as the " +"update notification runs once a week." +msgstr "" + +#: ../../content/administration/on_premise.rst:71 +msgid "Too many users error" +msgstr "" + +#: ../../content/administration/on_premise.rst:73 +msgid "" +"If you have more users in a local database than provisioned in your Odoo " +"Enterprise subscription, the following message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Too many users on a database error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:79 +msgid "" +"When the message appears, you have 30 days to act before the database " +"expires. The countdown is updated every day." +msgstr "" + +#: ../../content/administration/on_premise.rst:82 +#: ../../content/administration/on_premise.rst:102 +msgid "To resolve the issue, either:" +msgstr "" + +#: ../../content/administration/on_premise.rst:84 +msgid "" +"**Add more users** to your subscription by clicking the :guilabel:`Upgrade " +"your subscription` link displayed in the message to validate the upsell " +"quotation and pay for the extra users." +msgstr "" + +#: ../../content/administration/on_premise.rst:86 +msgid "" +":ref:`Deactivate users ` and **reject** the upsell " +"quotation." +msgstr "" + +#: ../../content/administration/on_premise.rst:88 +msgid "" +"Once your database has the correct number of users, the expiration message " +"disappears automatically after a few days, when the next verification " +"occurs." +msgstr "" + +#: ../../content/administration/on_premise.rst:92 +msgid "Database expired error" +msgstr "" + +#: ../../content/administration/on_premise.rst:94 +msgid "" +"If your database expires before you renew your subscription, the following " +"message should be displayed." +msgstr "" + +#: ../../content/administration/on_premise.rst:-1 +msgid "Database expired error message" +msgstr "" + +#: ../../content/administration/on_premise.rst:100 +msgid "" +"This message appears if you fail to act before the end of the 30-day " +"countdown." +msgstr "" + +#: ../../content/administration/on_premise.rst:104 +msgid "" +"Click the :guilabel:`Renew your subscription` link displayed in the message " +"and complete the process. If you pay by wire transfer, your subscription " +"will be renewed when the payment arrives which can take a few days. Credit " +"card payments are processed immediately." +msgstr "" + +#: ../../content/administration/on_premise.rst:107 +msgid "`Send a support ticket `_." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:6 +msgid "Switch from Community to Enterprise" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:8 +msgid "" +"Depending on your current installation, there are multiple ways to upgrade " +"your community version. In any case the basic guidelines are:" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:12 +#: ../../content/administration/on_premise/community_to_enterprise.rst:31 +#: ../../content/administration/on_premise/community_to_enterprise.rst:63 +#: ../../content/administration/on_premise/community_to_enterprise.rst:80 +msgid "Backup your community database" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:17 +#: ../../content/administration/on_premise/community_to_enterprise.rst:62 +msgid "Shutdown your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:19 +msgid "Install the web_enterprise module" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:21 +msgid "Restart your server" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:23 +msgid "Enter your Odoo Enterprise Subscription code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:29 +msgid "On Linux, using an installer" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:33 +msgid "Stop the odoo service" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:39 +msgid "" +"Install the enterprise .deb (it should install over the community package)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:45 +msgid "Update your database to the enterprise packages using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:51 +msgid "" +"You should be able to connect to your Odoo Enterprise instance using your " +"usual mean of identification. You can then link your database with your Odoo" +" Enterprise Subscription by entering the code you received by e-mail in the " +"form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:57 +msgid "On Linux, using the source code" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:59 +msgid "" +"There are many ways to launch your server when using sources, and you " +"probably have your own favourite. You may need to adapt sections to your " +"usual workflow." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:64 +msgid "" +"Update the ``--addons-path`` parameter of your launch command (see " +":doc:`../on_premise/source`)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:65 +msgid "Install the web_enterprise module by using" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:71 +msgid "Depending on the size of your database, this may take some time." +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:73 +msgid "" +"Restart your server with the updated addons path of point 3. You should be " +"able to connect to your instance. You can then link your database with your " +"Odoo Enterprise Subscription by entering the code you received by e-mail in " +"the form input" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:78 +msgid "On Windows" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:82 +msgid "" +"Uninstall Odoo Community (using the Uninstall executable in the installation" +" folder) - PostgreSQL will remain installed" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:88 +msgid "" +"Launch the Odoo Enterprise Installer and follow the steps normally. When " +"choosing the installation path, you can set the folder of the Community " +"installation (this folder still contains the PostgreSQL installation). " +"Uncheck ``Start Odoo`` at the end of the installation" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:96 +msgid "" +"Using a command window, update your Odoo Database using this command (from " +"the Odoo installation path, in the server subfolder)" +msgstr "" + +#: ../../content/administration/on_premise/community_to_enterprise.rst:103 +msgid "" +"No need to manually launch the server, the service is running. You should be" +" able to connect to your Odoo Enterprise instance using your usual mean of " +"identification. You can then link your database with your Odoo Enterprise " +"Subscription by entering the code you received by e-mail in the form input" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:3 +msgid "System configuration" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:5 +msgid "" +"This document describes basic steps to set up Odoo in production or on an " +"internet-facing server. It follows :doc:`installation <../on_premise>`, and " +"is not generally necessary for a development systems that is not exposed on " +"the internet." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:10 +msgid "" +"If you are setting up a public server, be sure to check our :ref:`security` " +"recommendations!" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:15 +msgid "dbfilter" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:17 +msgid "" +"Odoo is a multi-tenant system: a single Odoo system may run and serve a " +"number of database instances. It is also highly customizable, with " +"customizations (starting from the modules being loaded) depending on the " +"\"current database\"." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:21 +msgid "" +"This is not an issue when working with the backend (web client) as a logged-" +"in company user: the database can be selected when logging in, and " +"customizations loaded afterwards." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:25 +msgid "" +"However it is an issue for non-logged users (portal, website) which aren't " +"bound to a database: Odoo needs to know which database should be used to " +"load the website page or perform the operation. If multi-tenancy is not used" +" that is not an issue, there's only one database to use, but if there are " +"multiple databases accessible Odoo needs a rule to know which one it should " +"use." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:31 +msgid "" +"That is one of the purposes of :option:`--db-filter `:" +" it specifies how the database should be selected based on the hostname " +"(domain) that is being requested. The value is a `regular expression`_, " +"possibly including the dynamically injected hostname (``%h``) or the first " +"subdomain (``%d``) through which the system is being accessed." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:37 +msgid "" +"For servers hosting multiple databases in production, especially if " +"``website`` is used, dbfilter **must** be set, otherwise a number of " +"features will not work correctly." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:42 +msgid "Configuration samples" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:44 +msgid "Show only databases with names beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:46 +#: ../../content/administration/on_premise/deploy.rst:58 +#: ../../content/administration/on_premise/deploy.rst:153 +#: ../../content/administration/on_premise/deploy.rst:280 +msgid "in :ref:`the configuration file ` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:53 +msgid "" +"Show only databases matching the first subdomain after ``www``: for example " +"the database \"mycompany\" will be shown if the incoming request was sent to" +" ``www.mycompany.com`` or ``mycompany.co.uk``, but not for " +"``www2.mycompany.com`` or ``helpdesk.mycompany.com``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:67 +msgid "" +"Setting a proper :option:`--db-filter ` is an " +"important part of securing your deployment. Once it is correctly working and" +" only matching a single database per hostname, it is strongly recommended to" +" block access to the database manager screens, and to use the ``--no-" +"database-list`` startup parameter to prevent listing your databases, and to " +"block access to the database management screens. See also security_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:76 +#: ../../content/administration/on_premise/source.rst:193 +msgid "PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:78 +msgid "" +"By default, PostgreSQL only allows connection over UNIX sockets and loopback" +" connections (from \"localhost\", the same machine the PostgreSQL server is " +"installed on)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:82 +msgid "" +"UNIX socket is fine if you want Odoo and PostgreSQL to execute on the same " +"machine, and is the default when no host is provided, but if you want Odoo " +"and PostgreSQL to execute on different machines [#different-machines]_ it " +"will need to `listen to network interfaces`_ [#remote-socket]_, either:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:87 +msgid "" +"Only accept loopback connections and `use an SSH tunnel`_ between the " +"machine on which Odoo runs and the one on which PostgreSQL runs, then " +"configure Odoo to connect to its end of the tunnel" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:90 +msgid "" +"Accept connections to the machine on which Odoo is installed, possibly over " +"ssl (see `PostgreSQL connection settings`_ for details), then configure Odoo" +" to connect over the network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:95 +#: ../../content/administration/on_premise/deploy.rst:145 +#: ../../content/administration/on_premise/deploy.rst:235 +#: ../../content/administration/on_premise/deploy.rst:275 +msgid "Configuration sample" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:97 +msgid "Allow tcp connection on localhost" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:98 +msgid "Allow tcp connection from 192.168.1.x network" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:100 +msgid "in ``/etc/postgresql//main/pg_hba.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:108 +msgid "" +"in ``/etc/postgresql//main/postgresql.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:119 +msgid "Configuring Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:121 +msgid "" +"Out of the box, Odoo connects to a local postgres over UNIX socket via port " +"5432. This can be overridden using :ref:`the database options " +"` when your Postgres deployment is not " +"local and/or does not use the installation defaults." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:126 +msgid "" +"The :doc:`packaged installers ` will automatically create a new " +"user (``odoo``) and set it as the database user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:129 +msgid "" +"The database management screens are protected by the ``admin_passwd`` " +"setting. This setting can only be set using configuration files, and is " +"simply checked before performing database alterations. It should be set to a" +" randomly generated value to ensure third parties can not use this " +"interface." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:134 +msgid "" +"All database operations use the :ref:`database options " +"`, including the database management " +"screen. For the database management screen to work requires that the " +"PostgreSQL user have ``createdb`` right." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:138 +msgid "" +"Users can always drop databases they own. For the database management screen" +" to be completely non-functional, the PostgreSQL user needs to be created " +"with ``no-createdb`` and the database must be owned by a different " +"PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:142 +msgid "the PostgreSQL user *must not* be a superuser" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:147 +msgid "connect to a PostgreSQL server on 192.168.1.2" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:148 +msgid "port 5432" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:149 +msgid "using an 'odoo' user account," +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:150 +msgid "with 'pwd' as a password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:151 +msgid "filtering only db with a name beginning with 'mycompany'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:168 +msgid "SSL Between Odoo and PostgreSQL" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:170 +msgid "" +"Since Odoo 11.0, you can enforce ssl connection between Odoo and PostgreSQL." +" in Odoo the db_sslmode control the ssl security of the connection with " +"value chosen out of 'disable', 'allow', 'prefer', 'require', 'verify-ca' or " +"'verify-full'" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:175 +msgid "" +"`PostgreSQL Doc `_" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:180 +msgid "Builtin server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:182 +msgid "" +"Odoo includes built-in HTTP, cron, and live-chat servers, using either " +"multi-threading or multi-processing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:185 +msgid "" +"The **multi-threaded** server is a simpler server primarily used for " +"development, demonstrations, and its compatibility with various operating " +"systems (including Windows). A new thread is spawned for every new HTTP " +"request, even for long-lived connections such as websocket. Extra daemonic " +"cron threads are spawned too. Due to a Python limitation (GIL), it doesn't " +"make the best use of the hardware." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:191 +msgid "" +"The multi-threaded server is the default server, also for docker containers." +" It is selected by leaving the :option:`--workers ` " +"option out or setting it to ``0``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:194 +msgid "" +"The **multi-processing** server is a full-blown server primarily used for " +"production. It is not liable to the same Python limitation (GIL) on resource" +" usage and hence makes the best use of the hardware. A pool of workers is " +"created upon server startup. New HTTP requests are queued by the OS until " +"there are workers ready to process them. An extra event-driven HTTP worker " +"for the live chat is spawned on an alternative port. Extra cron workers are " +"spawned too. A configurable process reaper monitors resource usage and can " +"kill/restart failed workers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:201 +msgid "" +"The multi-processing server is opt-in. It is selected by setting the " +":option:`--workers ` option to a non-null integer." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:205 +msgid "" +"Because it is highly customized for Linux servers, the multi-processing " +"server is not available on Windows." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:209 +msgid "Worker number calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:211 +msgid "Rule of thumb : (#CPU * 2) + 1" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:212 +msgid "Cron workers need CPU" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:213 +msgid "1 worker ~= 6 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:216 +msgid "memory size calculation" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:218 +msgid "" +"We consider 20% of the requests are heavy requests, while 80% are simpler " +"ones" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:219 +msgid "" +"A heavy worker, when all computed field are well designed, SQL requests are " +"well designed, ... is estimated to consume around 1GB of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:220 +msgid "" +"A lighter worker, in the same scenario, is estimated to consume around 150MB" +" of RAM" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:222 +msgid "" +"Needed RAM = #worker * ( (light_worker_ratio * light_worker_ram_estimation) " +"+ (heavy_worker_ratio * heavy_worker_ram_estimation) )" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:225 +#: ../../content/administration/on_premise/deploy.rst:413 +msgid "LiveChat" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:227 +msgid "" +"In multi-processing, a dedicated LiveChat worker is automatically started " +"and listens on the :option:`--gevent-port `. By " +"default, the HTTP requests will keep accessing the normal HTTP workers " +"instead of the LiveChat one. You must deploy a proxy in front of Odoo and " +"redirect incoming requests whose path starts with ``/websocket/`` to the " +"LiveChat worker. You must also start Odoo in :option:`--proxy-mode ` so it uses the real client headers (such as hostname, " +"scheme, and IP) instead of the proxy ones." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:237 +msgid "Server with 4 CPU, 8 Thread" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:238 +msgid "60 concurrent users" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:240 +msgid "60 users / 6 = 10 <- theoretical number of worker needed" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:241 +msgid "(4 * 2) + 1 = 9 <- theoretical maximal number of worker" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:242 +msgid "" +"We'll use 8 workers + 1 for cron. We'll also use a monitoring system to " +"measure cpu load, and check if it's between 7 and 7.5 ." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:243 +msgid "RAM = 9 * ((0.8*150) + (0.2*1024)) ~= 3GB RAM for Odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:245 +msgid "in :ref:`the configuration file `:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:261 +msgid "HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:263 +msgid "" +"Whether it's accessed via website/web client or web service, Odoo transmits " +"authentication information in cleartext. This means a secure deployment of " +"Odoo must use HTTPS\\ [#switching]_. SSL termination can be implemented via " +"just about any SSL termination proxy, but requires the following setup:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:268 +msgid "" +"Enable Odoo's :option:`proxy mode `. This should only" +" be enabled when Odoo is behind a reverse proxy" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:269 +msgid "Set up the SSL termination proxy (`Nginx termination example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:270 +msgid "Set up the proxying itself (`Nginx proxying example`_)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:271 +msgid "" +"Your SSL termination proxy should also automatically redirect non-secure " +"connections to the secure port" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:277 +msgid "Redirect http requests to https" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:278 +msgid "Proxy requests to odoo" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:286 +msgid "in ``/etc/nginx/sites-enabled/odoo.conf`` set:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:362 +msgid "HTTPS Hardening" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:364 +msgid "" +"Add the `Strict-Transport-Security` header to all requests, in order to " +"prevent browsers from ever sending a plain HTTP request to this domain. You " +"will need to maintain a working HTTPS service with a valid certificate on " +"this domain at all times, otherwise your users will see security alerts or " +"be entirely unable to access it." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:370 +msgid "" +"Force HTTPS connections during a year for every visitor in NGINX with the " +"line:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:376 +msgid "" +"Additional configuration can be defined for the `session_id` cookie. The " +"`Secure` flag can be added to ensure it is never transmitted over HTTP and " +"`SameSite=Lax` to prevent authenticated `CSRF`_." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:387 +msgid "Odoo as a WSGI Application" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:389 +msgid "" +"It is also possible to mount Odoo as a standard WSGI_ application. Odoo " +"provides the base for a WSGI launcher script as ``odoo-wsgi.example.py``. " +"That script should be customized (possibly after copying it from the setup " +"directory) to correctly set the configuration directly in " +":mod:`odoo.tools.config` rather than through the command-line or a " +"configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:395 +msgid "" +"However the WSGI server will only expose the main HTTP endpoint for the web " +"client, website and webservice API. Because Odoo does not control the " +"creation of workers anymore it can not setup cron or livechat workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:400 +msgid "Cron Workers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:402 +msgid "" +"Starting one of the built-in Odoo servers next to the WSGI server is " +"required to process cron jobs. That server must be configured to only " +"process crons and not HTTP requests using the :option:`--no-http ` cli option or the ``http_enable = False`` configuration file " +"setting." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:407 +msgid "" +"On Linux-like systems, using the multi-processing server over the multi-" +"threading one is recommended to benefit from better hardware usage and " +"increased stability, i.e., using the :option:`--workers=-1 ` and :option:`--max-cron-threads=n `" +" cli options." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:415 +msgid "" +"Using a gevent-compatible WSGI server is required for the correct operation " +"of the live chat feature. That server should be able to handle many " +"simultaneous long-lived connections but doesn't need a lot of processing " +"power. All requests whose path starts with ``/websocket/`` should be " +"directed to that server. A regular (thread/process-based) WSGI server should" +" be used for all other requests." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:421 +msgid "" +"The Odoo cron server can also be used to serve the live chat requests. Just " +"drop the :option:`--no-http ` cli option from the cron " +"server and make sure requests whose path starts with ``/websocket/`` are " +"directed to this server, either on the :option:`--http-port ` (multi-threading server) or on the :option:`--gevent-port " +"` (multi-processing server)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:430 +msgid "Serving static files and attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:432 +msgid "" +"For development convenience, Odoo directly serves all static files and " +"attachments in its modules. This may not be ideal when it comes to " +"performances, and static files should generally be served by a static HTTP " +"server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:437 +msgid "Serving static files" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:439 +msgid "" +"Odoo static files are located in each module's :file:`static/` folder, so " +"static files can be served by intercepting all requests to " +":samp:`/{MODULE}/static/{FILE}`, and looking up the right module (and file) " +"in the various addons paths." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:443 +msgid "" +"It is recommended to set the ``Content-Security-Policy: default-src 'none'``" +" header on all images delivered by the web server. It is not strictly " +"necessary as users cannot modify/inject content inside of modules' " +":file:`static/` folder and existing images are final (they do not fetch new " +"resources by themselves). However, it is good practice." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:448 +msgid "" +"Using the above NGINX (https) configuration, the following ``map`` and " +"``location`` blocks should be added to serve static files via NGINX." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:475 +msgid "" +"The actual ``root`` and ``try_files`` directives are dependant on your " +"installation, specifically on your :option:`--addons-path `." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:482 +msgid "Debian package" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:484 +msgid "" +"Say Odoo has been installed via the **debian packages** for Community and " +"Enterprise, and that the :option:`--addons-path ` is" +" ``'/usr/lib/python3/dist-packages/odoo/addons'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:488 +#: ../../content/administration/on_premise/deploy.rst:502 +msgid "The ``root`` and ``try_files`` should be:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:495 +msgid "Git sources" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:497 +msgid "" +"Say Odoo has been installed via the **sources**, that both the Community and" +" Enterprise git repositories were cloned in :file:`/opt/odoo/community` and " +":file:`/opt/odoo/enterprise` respectively, and that the :option:`--addons-" +"path ` is " +"``'/opt/odoo/community/odoo/addons,/opt/odoo/community/addons,/opt/odoo/enterprise'``." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:510 +msgid "Serving attachments" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:512 +msgid "" +"Attachments are files stored in the filestore which access is regulated by " +"Odoo. They cannot be directly accessed via a static web server as accessing " +"them requires multiple lookups in the database to determine where the files " +"are stored and whether the current user can access them or not." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:517 +msgid "" +"Nevertheless, once the file has been located and the access rights verified " +"by Odoo, it is a good idea to serve the file using the static web server " +"instead of Odoo. For Odoo to delegate serving files to the static web " +"server, the `X-Sendfile `_ (apache) or " +"`X-Accel " +"`_ " +"(nginx) extensions must be enabled and configured on the static web server. " +"Once it is set up, start Odoo with the :option:`--x-sendfile ` CLI flag (this unique flag is used for both X-Sendfile and " +"X-Accel)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:527 +msgid "" +"The X-Sendfile extension for apache (and compatible web servers) does not " +"require any supplementary configuration." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:529 +msgid "" +"The X-Accel extension for NGINX **does** require the following additionnal " +"configuration:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:538 +msgid "" +"In case you don't know what is the path to your filestore, start Odoo with " +"the :option:`--x-sendfile ` option and navigate to " +"the ``/web/filestore`` URL directly via Odoo (don't navigate to the URL via " +"NGINX). This logs a warnings, the message contains the configuration you " +"need." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:547 +msgid "Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:549 +msgid "" +"For starters, keep in mind that securing an information system is a " +"continuous process, not a one-shot operation. At any moment, you will only " +"be as secure as the weakest link in your environment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:553 +msgid "" +"So please do not take this section as the ultimate list of measures that " +"will prevent all security problems. It's only intended as a summary of the " +"first important things you should be sure to include in your security action" +" plan. The rest will come from best security practices for your operating " +"system and distribution, best practices in terms of users, passwords, and " +"access control management, etc." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:559 +msgid "" +"When deploying an internet-facing server, please be sure to consider the " +"following security-related topics:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:562 +msgid "" +"Always set a strong super-admin admin password, and restrict access to the " +"database management pages as soon as the system is set up. See " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:565 +msgid "" +"Choose unique logins and strong passwords for all administrator accounts on " +"all databases. Do not use 'admin' as the login. Do not use those logins for " +"day-to-day operations, only for controlling/managing the installation. " +"*Never* use any default passwords like admin/admin, even for test/staging " +"databases." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:570 +msgid "" +"Do **not** install demo data on internet-facing servers. Databases with demo" +" data contain default logins and passwords that can be used to get into your" +" systems and cause significant trouble, even on staging/dev systems." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:574 +msgid "" +"Use appropriate database filters ( :option:`--db-filter `) to restrict the visibility of your databases according to the " +"hostname. See :ref:`dbfilter`. You may also use :option:`-d ` " +"to provide your own (comma-separated) list of available databases to filter " +"from, instead of letting the system fetch them all from the database " +"backend." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:581 +msgid "" +"Once your ``db_name`` and ``dbfilter`` are configured and only match a " +"single database per hostname, you should set ``list_db`` configuration " +"option to ``False``, to prevent listing databases entirely, and to block " +"access to the database management screens (this is also exposed as the " +":option:`--no-database-list ` command-line " +"option)" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:587 +msgid "" +"Make sure the PostgreSQL user (:option:`--db_user `) is " +"*not* a super-user, and that your databases are owned by a different user. " +"For example they could be owned by the ``postgres`` super-user if you are " +"using a dedicated non-privileged ``db_user``. See also " +":ref:`setup/deploy/odoo`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:592 +msgid "" +"Keep installations updated by regularly installing the latest builds, either" +" via GitHub or by downloading the latest version from " +"https://www.odoo.com/page/download or http://nightly.odoo.com" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:596 +msgid "" +"Configure your server in multi-process mode with proper limits matching your" +" typical usage (memory/CPU/timeouts). See also :ref:`builtin_server`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:599 +msgid "" +"Run Odoo behind a web server providing HTTPS termination with a valid SSL " +"certificate, in order to prevent eavesdropping on cleartext communications. " +"SSL certificates are cheap, and many free options exist. Configure the web " +"proxy to limit the size of requests, set appropriate timeouts, and then " +"enable the :option:`proxy mode ` option. See also " +":ref:`https_proxy`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:606 +msgid "" +"If you need to allow remote SSH access to your servers, make sure to set a " +"strong password for **all** accounts, not just `root`. It is strongly " +"recommended to entirely disable password-based authentication, and only " +"allow public key authentication. Also consider restricting access via a VPN," +" allowing only trusted IPs in the firewall, and/or running a brute-force " +"detection system such as `fail2ban` or equivalent." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:612 +msgid "" +"Consider installing appropriate rate-limiting on your proxy or firewall, to " +"prevent brute-force attacks and denial of service attacks. See also " +":ref:`login_brute_force` for specific measures." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:616 +msgid "" +"Many network providers provide automatic mitigation for Distributed Denial " +"of Service attacks (DDOS), but this is often an optional service, so you " +"should consult with them." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:620 +msgid "" +"Whenever possible, host your public-facing demo/test/staging instances on " +"different machines than the production ones. And apply the same security " +"precautions as for production." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:624 +msgid "" +"If your public-facing Odoo server has access to sensitive internal network " +"resources or services (e.g. via a private VLAN), implement appropriate " +"firewall rules to protect those internal resources. This will ensure that " +"the Odoo server cannot be used accidentally (or as a result of malicious " +"user actions) to access or disrupt those internal resources. Typically this " +"can be done by applying an outbound default DENY rule on the firewall, then " +"only explicitly authorizing access to internal resources that the Odoo " +"server needs to access. `Systemd IP traffic access control " +"`_ may also be useful to implement per-process network access " +"control." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:635 +msgid "" +"If your public-facing Odoo server is behind a Web Application Firewall, a " +"load-balancer, a transparent DDoS protection service (like CloudFlare) or a " +"similar network-level device, you may wish to avoid direct access to the " +"Odoo system. It is generally difficult to keep the endpoint IP addresses of " +"your Odoo servers secret. For example they can appear in web server logs " +"when querying public systems, or in the headers of emails posted from Odoo. " +"In such a situation you may want to configure your firewall so that the " +"endpoints are not accessible publicly except from the specific IP addresses " +"of your WAF, load-balancer or proxy service. Service providers like " +"CloudFlare usually maintain a public list of their IP address ranges for " +"this purpose." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:646 +msgid "" +"If you are hosting multiple customers, isolate customer data and files from " +"each other using containers or appropriate \"jail\" techniques." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:649 +msgid "" +"Setup daily backups of your databases and filestore data, and copy them to a" +" remote archiving server that is not accessible from the server itself." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:652 +msgid "" +"Deploying Odoo on Linux is strongly recommended over Windows. Should you " +"choose nevertheless to deploy on a Windows platform, a thorough security " +"hardening review of the server should be conducted and is outside of the " +"scope of this guide." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:660 +msgid "Blocking Brute Force Attacks" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:662 +msgid "" +"For internet-facing deployments, brute force attacks on user passwords are " +"very common, and this threat should not be neglected for Odoo servers. Odoo " +"emits a log entry whenever a login attempt is performed, and reports the " +"result: success or failure, along with the target login and source IP." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:666 +msgid "The log entries will have the following form." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:668 +msgid "Failed login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:672 +msgid "Successful login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:677 +msgid "" +"These logs can be easily analyzed by an intrusion prevention system such as " +"`fail2ban`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:679 +msgid "" +"For example, the following fail2ban filter definition should match a failed " +"login::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:686 +msgid "" +"This could be used with a jail definition to block the attacking IP on " +"HTTP(S)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:688 +msgid "" +"Here is what it could look like for blocking the IP for 15 minutes when 10 " +"failed login attempts are detected from the same IP within 1 minute::" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:702 +msgid "Database Manager Security" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:704 +msgid ":ref:`setup/deploy/odoo` mentioned ``admin_passwd`` in passing." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:706 +msgid "" +"This setting is used on all database management screens (to create, delete, " +"dump or restore databases)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:709 +msgid "" +"If the management screens must not be accessible at all, you should set " +"``list_db`` configuration option to ``False``, to block access to all the " +"database selection and management screens." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:715 +msgid "" +"It is strongly recommended to disable the Database Manager for any internet-" +"facing system! It is meant as a development/demo tool, to make it easy to " +"quickly create and manage databases. It is not designed for use in " +"production, and may even expose dangerous features to attackers. It is also " +"not designed to handle large databases, and may trigger memory limits." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:721 +msgid "" +"On production systems, database management operations should always be " +"performed by the system administrator, including provisioning of new " +"databases and automated backups." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:724 +msgid "" +"Be sure to setup an appropriate ``db_name`` parameter (and optionally, " +"``dbfilter`` too) so that the system can determine the target database for " +"each request, otherwise users will be blocked as they won't be allowed to " +"choose the database themselves." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:729 +msgid "" +"If the management screens must only be accessible from a selected set of " +"machines, use the proxy server's features to block access to all routes " +"starting with ``/web/database`` except (maybe) ``/web/database/selector`` " +"which displays the database-selection screen." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:733 +msgid "" +"If the database-management screen should be left accessible, the " +"``admin_passwd`` setting must be changed from its ``admin`` default: this " +"password is checked before allowing database-alteration operations." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:737 +msgid "It should be stored securely, and should be generated randomly e.g." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:743 +msgid "which generates a 32-character pseudorandom printable string." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:746 +msgid "Reset the master password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:748 +msgid "" +"There may be instances where the master password is misplaced, or " +"compromised, and needs to be reset. The following process is for system " +"administrators of an Odoo on-premise database detailing how to manually " +"reset and re-encrypt the master password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:753 +msgid "" +"For more information about changing an Odoo.com account password, see this " +"documentation: :ref:`odoocom/change_password`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:756 +msgid "" +"When creating a new on-premise database, a random master password is " +"generated. Odoo recommends using this password to secure the database. This " +"password is implemented by default, so there is a secure master password for" +" any Odoo on-premise deployment." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:761 +msgid "" +"When creating an Odoo on-premise database the installation is accessible to " +"anyone on the internet, until this password is set to secure the database." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:764 +msgid "" +"The master password is specified in the Odoo configuration file (`odoo.conf`" +" or `odoorc` (hidden file)). The Odoo master password is needed to modify, " +"create, or delete a database through the graphical user interface (GUI)." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:769 +msgid "Locate configuration file" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:771 +msgid "" +"First, open the Odoo configuration file (`odoo.conf` or `odoorc` (hidden " +"file))." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:775 +#: ../../content/administration/on_premise/packages.rst:148 +#: ../../content/administration/on_premise/source.rst:70 +#: ../../content/administration/on_premise/source.rst:133 +#: ../../content/administration/on_premise/source.rst:158 +#: ../../content/administration/on_premise/source.rst:180 +#: ../../content/administration/on_premise/source.rst:208 +#: ../../content/administration/on_premise/source.rst:239 +#: ../../content/administration/on_premise/source.rst:328 +#: ../../content/administration/on_premise/source.rst:397 +#: ../../content/administration/on_premise/source.rst:460 +msgid "Windows" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:777 +msgid "" +"The configuration file is located at: " +"`c:\\\\ProgramFiles\\\\Odoo{VERSION}\\\\server\\\\odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:779 +#: ../../content/administration/on_premise/packages.rst:25 +#: ../../content/administration/on_premise/source.rst:52 +#: ../../content/administration/on_premise/source.rst:129 +#: ../../content/administration/on_premise/source.rst:152 +#: ../../content/administration/on_premise/source.rst:174 +#: ../../content/administration/on_premise/source.rst:199 +#: ../../content/administration/on_premise/source.rst:228 +#: ../../content/administration/on_premise/source.rst:271 +#: ../../content/administration/on_premise/source.rst:388 +#: ../../content/administration/on_premise/source.rst:450 +msgid "Linux" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:781 +msgid "" +"Depending on how Odoo is installed on the Linux machine, the configuration " +"file is located in one of two different places:" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:784 +msgid "Package installation: `/etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:785 +msgid "Source installation: `~/.odoorc`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:788 +msgid "Change old password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:790 +msgid "" +"Once the appropriate file has been opened, proceed to modify the old " +"password in the configuration file to a temporary password." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:795 +#: ../../content/administration/on_premise/deploy.rst:843 +msgid "Graphical user interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:797 +msgid "" +"After locating the configuration file, open it using a (:abbr:`GUI " +"(graphical user interface)`). This can be achieved by simply double clicking" +" on the file. Then, the device should have a default :abbr:`GUI (graphical " +"user interface)` to open the file with." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:801 +msgid "" +"Next, modify the master password line `admin_passwd = $pbkdf2-sha…` to " +"`admin_passwd = newpassword1234`, for example. This password can be " +"anything, as long as it is saved temporarily. Make sure to modify all " +"characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:806 +#: ../../content/administration/on_premise/deploy.rst:825 +msgid "" +"The line appears like this: `admin_passwd = " +"$pbkdf2-sh39dji295.59mptrfW.9z6HkA$w9j9AMVmKAP17OosCqDxDv2hjsvzlLpF8Rra8I7p/b573hji540mk/.3ek0lg%kvkol6k983mkf/40fjki79m`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:810 +#: ../../content/administration/on_premise/deploy.rst:829 +msgid "The modified line appears like this: `admin_passwd = newpassword1234`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:812 +#: ../../content/administration/on_premise/deploy.rst:852 +msgid "Command-line interface" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:814 +msgid "" +"Modify the master password line using the following Unix command detailed " +"below." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:816 +msgid "" +"Connect to the Odoo server's terminal via Secure Shell (SSH) protocol, and " +"edit the configuration file. To modify the configuration file, enter the " +"following command: :command:`sudo nano /etc/odoo.conf`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:820 +msgid "" +"After opening the configuration file, modify the master password line " +"`admin_passwd = $pbkdf2-sha…` to `admin_passwd = newpassword1234`. This " +"password can be anything, as long as it is saved temporarily. Make sure to " +"modify all characters after the `=`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:832 +msgid "" +"It is essential that the password is changed to something else, rather than " +"triggering a new password reset by adding a semicolon `;` at the beginning " +"of the line. This ensures the database is secure throughout the entire " +"password reset process." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:837 +msgid "Restart Odoo server" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:839 +msgid "" +"After setting the temporary password, a restart of the Odoo server is " +"**required**." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:845 +msgid "" +"To restart the Odoo server, first, type `services` into the Windows " +":guilabel:`Search` bar. Then, select the :guilabel:`Services` application, " +"and scroll down to the :guilabel:`Odoo` service." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:849 +msgid "" +"Next, right click on :guilabel:`Odoo`, and select :guilabel:`Start` or " +":guilabel:`Restart`. This action manually restarts the Odoo server." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:854 +msgid "" +"Restart the Odoo server by typing the command: :command:`sudo service odoo15" +" restart`" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:857 +msgid "" +"Change the number after `odoo` to fit the specific version the server is " +"running on." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:860 +msgid "Use web interface to re-encrypt password" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:862 +msgid "" +"First, navigate to `/web/database/manager` or " +"`http://server_ip:port/web/database/manager` in a browser." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:866 +msgid "" +"Replace `server_ip` with the IP address of the database. Replace `port` with" +" the numbered port the database is accessible from." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:869 +msgid "" +"Next, click :guilabel:`Set Master Password`, and type in the previously-" +"selected temporary password into the :guilabel:`Master Password` field. " +"Following this step, type in a :guilabel:`New Master Password`. The " +":guilabel:`New Master Password` is hashed (or encrypted), once the " +":guilabel:`Continue` button is clicked." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:874 +msgid "" +"At this point, the password has been successfully reset, and a hashed " +"version of the new password now appears in the configuration file." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:878 +msgid "" +"For more information on Odoo database security, see this documentation: " +":ref:`db_manager_security`." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:882 +msgid "Supported Browsers" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:884 +msgid "Odoo supports the latest version of the following browsers." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:886 +msgid "Google Chrome" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:887 +msgid "Mozilla Firefox" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:888 +msgid "Microsoft Edge" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:889 +msgid "Apple Safari" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:892 +msgid "" +"to have multiple Odoo installations use the same PostgreSQL database, or to " +"provide more computing resources to both software." +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:895 +msgid "" +"technically a tool like socat_ can be used to proxy UNIX sockets across " +"networks, but that is mostly for software which can only be used over UNIX " +"sockets" +msgstr "" + +#: ../../content/administration/on_premise/deploy.rst:899 +msgid "" +"or be accessible only over an internal packet-switched network, but that " +"requires secured switches, protections against `ARP spoofing`_ and precludes" +" usage of WiFi. Even over secure packet-switched networks, deployment over " +"HTTPS is recommended, and possible costs are lowered as \"self-signed\" " +"certificates are easier to deploy on a controlled environment than over the " +"internet." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:3 +msgid "Email gateway" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:5 +msgid "" +"The Odoo mail gateway allows you to inject directly all the received emails " +"in Odoo." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:7 +msgid "" +"Its principle is straightforward: your SMTP server executes the \"mailgate\"" +" script for every new incoming email." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:10 +msgid "" +"The script takes care of connecting to your Odoo database through XML-RPC, " +"and send the emails via the `MailThread.message_process()` feature." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:14 +msgid "Prerequisites" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:16 +msgid "Administrator access to the Odoo database." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:17 +msgid "Your own mail server such as Postfix or Exim." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:18 +msgid "Technical knowledge on how to configure an email server." +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:21 +msgid "For Postfix" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:23 +msgid "In you alias config (:file:`/etc/aliases`):" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:30 +#: ../../content/administration/on_premise/email_gateway.rst:44 +msgid "Resources" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:32 +msgid "`Postfix `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:33 +msgid "`Postfix aliases `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:34 +msgid "`Postfix virtual `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:37 +msgid "For Exim" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:46 +msgid "`Exim `_" +msgstr "" + +#: ../../content/administration/on_premise/email_gateway.rst:49 +msgid "" +"If you do not have access/manage your email server, use :ref:`incoming mail " +"servers `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:3 +msgid "Geo IP" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:6 +msgid "This documentation only applies to On-premise databases." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:15 +msgid "Move the files to the folder :file:`/usr/share/GeoIP/`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:22 +msgid "Restart the server" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:36 +msgid ":doc:`CLI documentation `." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:39 +msgid "Test GeoIP geolocation in your Odoo website" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:44 +msgid "Go to your website. Open the web page that you want to test ``GeoIP``." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:45 +msgid "Choose :menuselection:`Customize --> HTML/CSS/JS Editor`." +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:46 +msgid "Add the following piece of XML in the page :" +msgstr "" + +#: ../../content/administration/on_premise/geo_ip.rst:52 +msgid "Save and refresh the page." +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/geo_ip.rst:56 +msgid "" +"In case you read \"**geoip failure**\" instead then the geolocalization " +"failed. The common causes are:" +msgstr "" + +#: ../../content/administration/on_premise/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/on_premise/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/on_premise/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/on_premise/packages.rst:3 +msgid "Packaged installers" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:5 +msgid "" +"Odoo provides packaged installers for Debian-based Linux distributions " +"(Debian, Ubuntu, etc.), RPM-based Linux distributions (Fedora, CentOS, RHEL," +" etc.), and Windows for the Community and Enterprise editions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:9 +msgid "" +"Official **Community** nightly packages with all relevant dependency " +"requirements are available on the `nightly server " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:13 +msgid "Nightly packages may be difficult to keep up to date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:15 +msgid "" +"Official **Community** and **Enterprise** packages can be downloaded from " +"the `Odoo download page `_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:19 +msgid "" +"It is required to be logged in as a paying on-premise customer or partner to" +" download the Enterprise packages." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:28 +#: ../../content/administration/on_premise/source.rst:116 +msgid "Prepare" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:30 +msgid "" +"Odoo needs a `PostgreSQL `_ server to run " +"properly." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:34 +#: ../../content/administration/on_premise/packages.rst:70 +#: ../../content/administration/on_premise/packages.rst:100 +#: ../../content/administration/on_premise/source.rst:278 +msgid "Debian/Ubuntu" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:36 +msgid "" +"The default configuration for the Odoo 'deb' package is to use the " +"PostgreSQL server on the same host as the Odoo instance. Execute the " +"following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:44 +#: ../../content/administration/on_premise/packages.rst:80 +#: ../../content/administration/on_premise/packages.rst:132 +msgid "Fedora" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:46 +msgid "" +"Make sure that the `sudo` command is available and well configured and, only" +" then, execute the following command to install the PostgreSQL server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:57 +#: ../../content/administration/on_premise/source.rst:420 +msgid "" +"`wkhtmltopdf` is not installed through **pip** and must be installed " +"manually in `version 0.12.6 " +"`_ for it " +"to support headers and footers. Check out the `wkhtmltopdf wiki " +"`_ for more details on the " +"various versions." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:63 +msgid "Repository" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:65 +msgid "" +"Odoo S.A. provides a repository that can be used to install the " +"**Community** edition by executing the following commands:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:78 +msgid "" +"Use the usual `apt-get upgrade` command to keep the installation up-to-date." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:90 +msgid "Currently, there is no nightly repository for the Enterprise edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:93 +msgid "Distribution package" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:95 +msgid "" +"Instead of using the repository, packages for both the **Community** and " +"**Enterprise** editions can be downloaded from the `Odoo download page " +"`_." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:103 +msgid "" +"Odoo 18 'deb' package currently supports `Debian Bookworm (12) " +"`_ and `Ubuntu Jammy (22.04LTS) " +"`_ or above." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:107 +msgid "" +"Once downloaded, execute the following commands **as root** to install Odoo " +"as a service, create the necessary PostgreSQL user, and automatically start " +"the server:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:117 +msgid "" +"The `python3-xlwt` Debian package, needed to export into the XLS format, " +"does not exist in Debian Buster nor Ubuntu 18.04. If needed, install it " +"manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:124 +msgid "" +"The `num2words` Python package - needed to render textual amounts - does not" +" exist in Debian Buster nor Ubuntu 18.04, which could cause problems with " +"the `l10n_mx_edi` module. If needed, install it manually with the following:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:135 +msgid "Odoo 18 'rpm' package supports Fedora 38." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:137 +msgid "" +"Once downloaded, the package can be installed using the 'dnf' package " +"manager:" +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:151 +msgid "" +"Windows packaging is offered for the convenience of testing or running " +"single-user local instances but production deployment is discouraged due to " +"a number of limitations and risks associated with deploying Odoo on a " +"Windows platform." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:155 +msgid "" +"Download the installer from the `nightly server `_" +" (Community only) or the Windows installer from the `Odoo download page " +"`_ (any edition." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:158 +msgid "Execute the downloaded file." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:161 +msgid "" +"On Windows 8 and later, a warning titled *Windows protected your PC* may be " +"displayed. Click **More Info** and then **Run anyway** to proceed." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:164 +msgid "" +"Accept the `UAC `_ " +"prompt." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:165 +msgid "Go through the installation steps." +msgstr "" + +#: ../../content/administration/on_premise/packages.rst:167 +msgid "Odoo launches automatically at the end of the installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:3 +msgid "Source install" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:5 +msgid "" +"The source 'installation' is not about installing Odoo but running it " +"directly from the source instead." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:8 +msgid "" +"Using the Odoo source can be more convenient for module developers as it is " +"more easily accessible than using packaged installers." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:11 +msgid "" +"It makes starting and stopping Odoo more flexible and explicit than the " +"services set up by the packaged installers. Also, it allows overriding " +"settings using :ref:`command-line parameters ` without " +"needing to edit a configuration file." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:15 +msgid "" +"Finally, it provides greater control over the system's setup and allows to " +"more easily keep (and run) multiple versions of Odoo side-by-side." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:19 +msgid "Fetch the sources" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:21 +msgid "" +"There are two ways to obtain the source code of Odoo: as a ZIP **archive** " +"or through **Git**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:24 +msgid "Archive" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:26 +msgid "Community edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:28 +#: ../../content/administration/on_premise/source.rst:34 +msgid "`Odoo download page `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:29 +msgid "`GitHub Community repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:30 +msgid "`Nightly server `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:32 +msgid "Enterprise edition:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:35 +msgid "`GitHub Enterprise repository `_" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:40 +msgid "Git" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:43 +msgid "" +"It is required to have `Git `_ installed, and it is " +"recommended to have a basic knowledge of Git commands to proceed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:46 +msgid "" +"To clone a Git repository, choose between cloning with HTTPS or SSH. In most" +" cases, the best option is HTTPS. However, choose SSH to contribute to Odoo " +"source code or when following the :doc:`Getting Started developer tutorial " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:56 +#: ../../content/administration/on_premise/source.rst:74 +#: ../../content/administration/on_premise/source.rst:92 +msgid "Clone with HTTPS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:63 +#: ../../content/administration/on_premise/source.rst:81 +#: ../../content/administration/on_premise/source.rst:99 +msgid "Clone with SSH" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:88 +#: ../../content/administration/on_premise/source.rst:141 +#: ../../content/administration/on_premise/source.rst:164 +#: ../../content/administration/on_premise/source.rst:186 +#: ../../content/administration/on_premise/source.rst:213 +#: ../../content/administration/on_premise/source.rst:253 +#: ../../content/administration/on_premise/source.rst:351 +#: ../../content/administration/on_premise/source.rst:409 +#: ../../content/administration/on_premise/source.rst:471 +msgid "Mac OS" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:107 +msgid "" +"**The Enterprise git repository does not contain the full Odoo source " +"code**. It is only a collection of extra add-ons. The main server code is in" +" the Community edition. Running the Enterprise version means running the " +"server from the Community version with the `addons-path` option set to the " +"folder with the Enterprise edition. It is required to clone both the " +"Community and Enterprise repositories to have a working Odoo Enterprise " +"installation." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:119 +msgid "Python" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:121 +msgid "Odoo requires **Python 3.10** or later to run." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:123 +msgid "Minimum requirement updated from Python 3.7 to Python 3.10." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:131 +msgid "Use a package manager to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:135 +msgid "" +"`Download the latest version of Python 3 " +"`_ and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:138 +msgid "" +"During installation, check **Add Python 3 to PATH**, then click **Customize " +"Installation** and make sure that **pip** is checked." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:143 +msgid "" +"Use a package manager (`Homebrew `_, `MacPorts " +"`_) to download and install Python 3 if needed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:147 +msgid "" +"If Python 3 is already installed, make sure that the version is 3.10 or " +"above, as previous versions are not compatible with Odoo." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:170 +msgid "" +"Verify that `pip `_ is also installed for this version." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:195 +msgid "Odoo uses PostgreSQL as its database management system." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:201 +msgid "" +"Use a package manager to download and install PostgreSQL (supported " +"versions: 12.0 or above). It can be achieved by executing the following:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:210 +msgid "" +"`Download PostgreSQL `_ " +"(supported versions: 12.0 or above) and install it." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:215 +msgid "" +"Use `Postgres.app `_ to download and install " +"PostgreSQL (supported version: 12.0 or above)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:219 +msgid "" +"To make the command line tools bundled with Postgres.app available, make " +"sure to set up the `$PATH` variable by following the `Postgres.app CLI tools" +" instructions `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:223 +msgid "" +"By default, the only user is `postgres`. As Odoo forbids connecting as " +"`postgres`, create a new PostgreSQL user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:236 +#: ../../content/administration/on_premise/source.rst:261 +msgid "" +"Because the PostgreSQL user has the same name as the Unix login, it is " +"possible to connect to the database without a password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:241 +msgid "" +"Add PostgreSQL's `bin` directory (by default: :file:`C:\\\\Program " +"Files\\\\PostgreSQL\\\\\\\\bin`) to the `PATH`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:243 +msgid "Create a postgres user with a password using the pg admin gui:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:245 +msgid "Open **pgAdmin**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:246 +msgid "Double-click the server to create a connection." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:247 +msgid "Select :menuselection:`Object --> Create --> Login/Group Role`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:248 +msgid "Enter the username in the **Role Name** field (e.g., `odoo`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:249 +msgid "" +"Open the **Definition** tab, enter a password (e.g., `odoo`), and click " +"**Save**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:250 +msgid "" +"Open the **Privileges** tab and switch **Can login?** to `Yes` and **Create " +"database?** to `Yes`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:267 +msgid "Dependencies" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:273 +msgid "" +"Using **distribution packages** is the preferred way of installing " +"dependencies. Alternatively, install the Python dependencies with **pip**." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:280 +msgid "" +"On Debian/Ubuntu, the following commands should install the required " +"packages:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:287 +msgid "" +"The `setup/debinstall.sh` script will parse the `debian/control " +"`_ file and install " +"the found packages." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:290 +msgid "Install with pip" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:293 +msgid "" +"Using pip may lead to security issues and broken dependencies; only do this " +"if you know what you are doing." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:296 +msgid "" +"As some of the Python packages need a compilation step, they require system " +"libraries to be installed." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:299 +msgid "" +"On Debian/Ubuntu, the following command should install these required " +"libraries:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:305 +msgid "" +"Odoo dependencies are listed in the :file:`requirements.txt` file located at" +" the root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:309 +msgid "" +"The Python packages in :file:`requirements.txt` are based on their " +"stable/LTS Debian/Ubuntu corresponding version at the moment of the Odoo " +"release. For example, for Odoo 15.0, the `python3-babel` package version is " +"2.8.0 in Debian Bullseye and 2.6.0 in Ubuntu Focal. The lowest version is " +"then chosen in the :file:`requirements.txt`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:316 +#: ../../content/administration/on_premise/source.rst:338 +#: ../../content/administration/on_premise/source.rst:357 +msgid "" +"It can be preferable not to mix Python module packages between different " +"instances of Odoo or with the system. However, it is possible to use " +"`virtualenv `_ to create isolated " +"Python environments." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:320 +msgid "" +"Navigate to the path of the Odoo Community installation " +"(:file:`CommunityPath`) and run **pip** on the requirements file to install " +"the requirements for the current user." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:330 +msgid "" +"Before installing the dependencies, download and install the `Build Tools " +"for Visual Studio `_. Select " +"**C++ build tools** in the **Workloads** tab and install them when prompted." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:334 +#: ../../content/administration/on_premise/source.rst:353 +msgid "" +"Odoo dependencies are listed in the `requirements.txt` file located at the " +"root of the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:342 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file in a terminal **with Administrator " +"privileges**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:361 +msgid "" +"Navigate to the path of the Odoo Community installation (`CommunityPath`) " +"and run **pip** on the requirements file:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:371 +msgid "" +"Non-Python dependencies must be installed with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:374 +msgid "Download and install the **Command Line Tools**:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:380 +msgid "Use the package manager to install non-Python dependencies." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:383 +msgid "" +"For languages using a **right-to-left interface** (such as Arabic or " +"Hebrew), the `rtlcss` package is required." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:390 +msgid "Download and install **nodejs** and **npm** with a package manager." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:391 +#: ../../content/administration/on_premise/source.rst:400 +#: ../../content/administration/on_premise/source.rst:413 +msgid "Install `rtlcss`:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:399 +msgid "Download and install `nodejs `_." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:406 +msgid "" +"Edit the system environment's variable `PATH` to add the folder where " +"`rtlcss.cmd` is located (typically: " +":file:`C:\\\\Users\\\\\\\\AppData\\\\Roaming\\\\npm\\\\`)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:411 +msgid "" +"Download and install **nodejs** with a package manager (`Homebrew " +"`_, `MacPorts `_)." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:428 +msgid "Running Odoo" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:430 +msgid "" +"Once all dependencies are set up, Odoo can be launched by running `odoo-" +"bin`, the command-line interface of the server. It is located at the root of" +" the Odoo Community directory." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:433 +msgid "" +"To configure the server, either specify :ref:`command-line arguments " +"` or a :ref:`configuration file " +"`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:437 +msgid "" +"For the Enterprise edition, add the path to the `enterprise` add-ons to the " +"`addons-path` argument. Note that it must come before the other paths in " +"`addons-path` for add-ons to be loaded correctly." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:441 +msgid "Common necessary configurations are:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:443 +msgid "PostgreSQL user and password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:444 +msgid "Custom addon paths beyond the defaults to load custom modules." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:446 +msgid "A typical way to run the server would be:" +msgstr "" + +#: ../../content/administration/on_premise/source.rst:457 +#: ../../content/administration/on_premise/source.rst:478 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, and " +"`mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:467 +msgid "" +"Where `CommunityPath` is the path of the Odoo Community installation, " +"`dbuser` is the PostgreSQL login, `dbpassword` is the PostgreSQL password, " +"and `mydb` is the name of the PostgreSQL database." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:481 +msgid "" +"After the server has started (the INFO log `odoo.modules.loading: Modules " +"loaded.` is printed), open http://localhost:8069 in a web browser and log " +"into the Odoo database with the base administrator account: use `admin` as " +"the email and, again, `admin` as the password." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:486 +msgid "" +"From there, create and manage new :doc:`users " +"<../../applications/general/users>`." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:487 +msgid "" +"The user account used to log into Odoo's web interface differs from the " +":option:`--db_user ` CLI argument." +msgstr "" + +#: ../../content/administration/on_premise/source.rst:491 +msgid "" +":doc:`The list of CLI arguments for odoo-bin `" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:6 +msgid "Bugfix updates" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:9 +msgid "Introduction" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:11 +msgid "" +"In order to benefit from the latest improvements, security fixes, bug " +"corrections and performance boosts, you may need to update your Odoo " +"installation from time to time." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:14 +msgid "" +"This guide only applies when are using Odoo on your own hosting " +"infrastructure. If you are using one of the Odoo Cloud solutions, updates " +"are automatically performed for you." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:17 +msgid "" +"The terminology surrounding software updates is often confusing, so here are" +" some preliminary definitions:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:25 +msgid "Updating (an Odoo installation)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:21 +msgid "" +"Refers to the process of obtaining the latest revision of the source code " +"for your current Odoo Edition. For example, updating your Odoo Enterprise " +"13.0 to the latest revision. This does not directly cause any change to the " +"contents of your Odoo database, and can be undone by reinstalling the " +"previous revision of the source code." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:35 +msgid "Upgrading (an Odoo database)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:28 +msgid "" +"Refers to a complex data processing operation where the structure and " +"contents of your database is permanently altered to make it compatible with " +"a new release of Odoo. This operation is irreversible and typically " +"accomplished via Odoo's `database upgrade service " +"`_, when you decide to switch to a newer release " +"of Odoo. Historically, this process has also been known as a \"migration\" " +"because it involves moving data around inside the database, even though the " +"database may end up at the same physical location after the upgrade." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:37 +msgid "" +"This page describes the typical steps needed to *update* an Odoo " +"installation to the latest version. If you'd like more information about " +"upgrading a database, please visit the `Odoo Upgrade page " +"`_ instead." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:43 +msgid "In a nutshell" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:45 +msgid "" +"Updating Odoo is accomplished by simply reinstalling the latest version of " +"your Odoo Edition on top of your current installation. This will preserve " +"your data without any alteration, as long as you do not uninstall PostgreSQL" +" (the database engine that comes with Odoo)." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:49 +msgid "" +"The main reference for updating is logically our :doc:`installation guide " +"<../on_premise>`, which explains the common installation methods." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:52 +msgid "" +"Updating is also most appropriately accomplished by the person who deployed " +"Odoo initially, because the procedure is very similar." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:55 +msgid "" +"We always recommend to download a complete new up-to-date Odoo version, " +"rather than manually applying patches, such as the security patches that " +"come with Security Advisories. The patches are mainly provided for " +"installations that are heavily customized, or for technical personnel who " +"prefer to apply minimal changes temporarily while testing a complete update." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:64 +msgid "Step 1: Download an updated Odoo version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:66 +msgid "" +"The central download page is https://www.odoo.com/page/download. If you see " +"a \"Buy\" link for the Odoo Enterprise download, make sure you are logged " +"into Odoo.com with the same login that is linked to your Odoo Enterprise " +"subscription." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:70 +msgid "" +"Alternatively, you can use the unique download link that was included with " +"your Odoo Enterprise purchase confirmation email." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:73 +msgid "" +"Downloading an updated version is not necessary if you installed via Github " +"(see below)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:77 +msgid "Step 2: Make a backup of your database" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:79 +msgid "" +"The update procedure is quite safe and should not alter you data. However " +"it's always best to take a full database backup before performing any change" +" on your installation, and to store it somewhere safe, on a different " +"computer." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:83 +msgid "" +"If you have not disabled the database manager screen (see :ref:`here " +"` why you should), you can use it (link at bottom of your database" +" selection screen) to download a backup of your database(s). If you disabled" +" it, use the same procedure than for your usual backups." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:89 +msgid "Step 3: Install the updated version" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:91 +msgid "Choose the method that matches your current installation:" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:95 +msgid "Packaged Installers" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:97 +msgid "" +"If you installed Odoo with an installation package downloaded on our website" +" (the recommended method), updating is very simple. All you have to do is " +"download the installation package corresponding to your system (see step #1)" +" and install it on your server. They are updated daily and include the " +"latest security fixes. Usually, you can simply double-click the package to " +"install it on top of the current installation. After installing the package," +" be sure to restart the Odoo service or reboot your server, and you're all " +"set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:106 +msgid "Source Install (Tarball)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:108 +msgid "" +"If you have originally installed Odoo with the \"tarball\" version (source " +"code archive), you have to replace the installation directory with a newer " +"version. First download the latest tarball from Odoo.com. They are updated " +"daily and include the latest security fixes (see step #1) After downloading " +"the package, extract it to a temporary location on your server." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:113 +msgid "" +"You will get a folder labeled with the version of the source code, for " +"example \"odoo-13.0+e.20190719\", that contains a folder \"odoo.egg-info\" " +"and the actual source code folder named \"odoo\" (for Odoo 10 and later) or " +"\"openerp\" for older versions. You can ignore the odoo.egg-info folder. " +"Locate the folder where your current installation is deployed, and replace " +"it with the newer \"odoo\" or \"openerp\" folder that was in the archive you" +" just extracted." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:119 +msgid "" +"Be sure to match the folder layout, for example the new \"addons\" folder " +"included in the source code should end up exactly at the same path it was " +"before. Next, watch out for any specific configuration files that you may " +"have manually copied or modified in the old folder, and copy them over to " +"the new folder. Finally, restart the Odoo service or reboot the machine, and" +" you are all set." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:126 +msgid "Source Install (Github)" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:128 +msgid "" +"If you have originally installed Odoo with a full Github clone of the " +"official repositories, the update procedure requires you to pull the latest " +"source code via git. Change into the directory for each repository (the main" +" Odoo repository, and the Enterprise repository), and run the following " +"commands::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:136 +msgid "" +"The last command may encounter source code conflicts if you had edited the " +"Odoo source code locally. The error message will give you the list of files " +"with conflicts, and you will need to resolve the conflicts manually, by " +"editing them and deciding which part of the code to keep." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:140 +msgid "" +"Alternatively, if you prefer to simply discard the conflicting changes and " +"restore the official version, you can use the following command::" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:145 +msgid "" +"Finally, restart the Odoo service or reboot the machine, and you should be " +"done." +msgstr "" + +#: ../../content/administration/on_premise/update.rst:149 +msgid "Docker" +msgstr "" + +#: ../../content/administration/on_premise/update.rst:151 +msgid "" +"Please refer to our `Docker image documentation " +"`_ for specific update instructions." +msgstr "" + +#: ../../content/administration/supported_versions.rst:7 +msgid "Supported versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:9 +msgid "" +"Odoo provides support and bug fixing **for the 3 last major versions** of " +"Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:12 +msgid "" +"Odoo releases intermediary versions called **Online versions** on the " +":doc:`Odoo Online ` hosting every two months. Odoo Online users" +" can then benefit from the latest features of Odoo." +msgstr "" + +#: ../../content/administration/supported_versions.rst:16 +msgid "" +"Admins of Odoo Online databases are invited to :doc:`upgrade ` them" +" regularly." +msgstr "" + +#: ../../content/administration/supported_versions.rst:17 +msgid "" +"Online versions are *not* released for Odoo.sh and On-Premise installations." +msgstr "" + +#: ../../content/administration/supported_versions.rst:18 +msgid "Online versions are listed below as *SaaS*." +msgstr "" + +#: ../../content/administration/supported_versions.rst:20 +msgid "This matrix shows the support status of every version." +msgstr "" + +#: ../../content/administration/supported_versions.rst:22 +msgid "**Major releases are in bold type.**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:31 +msgid "On-Premise" +msgstr "" + +#: ../../content/administration/supported_versions.rst:32 +msgid "Release date" +msgstr "" + +#: ../../content/administration/supported_versions.rst:33 +msgid "End of support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:34 +msgid "Odoo SaaS 18.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:36 +#: ../../content/administration/supported_versions.rst:37 +#: ../../content/administration/supported_versions.rst:42 +#: ../../content/administration/supported_versions.rst:43 +#: ../../content/administration/supported_versions.rst:48 +#: ../../content/administration/supported_versions.rst:49 +#: ../../content/administration/supported_versions.rst:54 +#: ../../content/administration/supported_versions.rst:55 +#: ../../content/administration/supported_versions.rst:66 +#: ../../content/administration/supported_versions.rst:67 +#: ../../content/administration/supported_versions.rst:72 +#: ../../content/administration/supported_versions.rst:73 +msgid "N/A" +msgstr "" + +#: ../../content/administration/supported_versions.rst:38 +msgid "July 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:40 +msgid "Odoo SaaS 18.3" +msgstr "" + +#: ../../content/administration/supported_versions.rst:44 +msgid "May 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:46 +msgid "Odoo SaaS 18.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:50 +msgid "March 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:52 +msgid "Odoo SaaS 18.1" +msgstr "" + +#: ../../content/administration/supported_versions.rst:56 +msgid "January 2025" +msgstr "" + +#: ../../content/administration/supported_versions.rst:58 +msgid "**Odoo 18.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:62 +#: ../../content/administration/supported_versions.rst:69 +#: ../../content/administration/supported_versions.rst:75 +#: ../../content/administration/supported_versions.rst:93 +msgid "October 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:63 +msgid "October 2027 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:64 +msgid "Odoo SaaS 17.4" +msgstr "" + +#: ../../content/administration/supported_versions.rst:65 +#: ../../content/administration/supported_versions.rst:71 +#: ../../content/administration/supported_versions.rst:89 +#: ../../content/administration/supported_versions.rst:90 +#: ../../content/administration/supported_versions.rst:91 +#: ../../content/administration/supported_versions.rst:95 +#: ../../content/administration/supported_versions.rst:96 +#: ../../content/administration/supported_versions.rst:97 +msgid "|red|" +msgstr "" + +#: ../../content/administration/supported_versions.rst:68 +msgid "July 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:70 +msgid "Odoo SaaS 17.2" +msgstr "" + +#: ../../content/administration/supported_versions.rst:74 +msgid "April 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:76 +msgid "**Odoo 17.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:80 +msgid "November 2023" +msgstr "" + +#: ../../content/administration/supported_versions.rst:81 +msgid "October 2026 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:82 +msgid "**Odoo 16.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:86 +msgid "October 2022" +msgstr "" + +#: ../../content/administration/supported_versions.rst:87 +msgid "October 2025 (planned)" +msgstr "" + +#: ../../content/administration/supported_versions.rst:88 +msgid "**Odoo 15.0**" +msgstr "" + +#: ../../content/administration/supported_versions.rst:92 +msgid "October 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:94 +msgid "Older versions" +msgstr "" + +#: ../../content/administration/supported_versions.rst:98 +msgid "Before 2021" +msgstr "" + +#: ../../content/administration/supported_versions.rst:99 +msgid "Before 2024" +msgstr "" + +#: ../../content/administration/supported_versions.rst:101 +msgid "Legend" +msgstr "" + +#: ../../content/administration/supported_versions.rst:103 +msgid "|green| Supported version" +msgstr "" + +#: ../../content/administration/supported_versions.rst:105 +msgid "|red| End-of-support" +msgstr "" + +#: ../../content/administration/supported_versions.rst:107 +msgid "N/A Never released for this platform" +msgstr "" + +#: ../../content/administration/supported_versions.rst:110 +msgid "" +"Even though we don't support older versions, you can always `upgrade from " +"any version `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:5 +msgid "" +"An upgrade involves moving a database from an older version to a newer " +"supported version (e.g., from Odoo 16.0 to Odoo 18.0). Regular upgrades are " +"crucial as each version offers new features, bug fixes, and security " +"patches. Using a :doc:`supported version ` is strongly " +"recommended. Each major version is supported for three years." +msgstr "" + +#: ../../content/administration/upgrade.rst:10 +msgid "" +"Depending on the hosting type and Odoo version used, a database upgrade can " +"be **mandatory**." +msgstr "" + +#: ../../content/administration/upgrade.rst:16 +msgid "" +"If a database is on a **major version** (e.g., 16.0, 17.0, 18.0), an upgrade" +" is mandatory every two years." +msgstr "" + +#: ../../content/administration/upgrade.rst:18 +msgid "" +"If a database is on a **minor version** (e.g., 17.1, 17.2, 17.4), an upgrade" +" is mandatory a few weeks after the next version is released. Minor versions" +" are usually released every two months." +msgstr "" + +#: ../../content/administration/upgrade.rst:24 +msgid "" +"After the initial three years of support, you will have another two years to" +" complete the upgrade. You will be notified when an upgrade is required." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"unsupported version\" popup on Odoo.sh." +msgstr "" + +#: ../../content/administration/upgrade.rst:32 +msgid "" +"You can stay on the same version indefinitely, even if it is not " +"recommended. Note that the smaller the version gap, the easier the upgrade " +"should be." +msgstr "" + +#: ../../content/administration/upgrade.rst:37 +msgid "" +"You will receive a notification in your database a few weeks before a " +"mandatory upgrade will be automatically carried out. You are in control of " +"the process as long as the deadline is not reached." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The upgrade message prompt on the top right of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:44 +msgid "" +"Concretely, Odoo’s Upgrade Team performs a silent test upgrade of every " +"database that should be upgraded. If the test is successful and lasts less " +"than 20 minutes, you can directly trigger the upgrade from the database. If " +"the test fails, you can test an upgrade using the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:49 +msgid "" +"When you are invited to upgrade, it is strongly recommended to :ref:`request" +" an upgraded test database ` first and spend time " +":ref:`testing ` it." +msgstr "" + +#: ../../content/administration/upgrade.rst:52 +msgid "" +"An automatic upgrade to the next version will be triggered if no action is " +"taken before the specified due date." +msgstr "" + +#: ../../content/administration/upgrade.rst:55 +msgid "An upgrade does not cover:" +msgstr "" + +#: ../../content/administration/upgrade.rst:57 +msgid "Downgrading to a previous version of Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:58 +msgid "" +":doc:`Switching editions ` (e.g., from " +"Community to Enterprise)" +msgstr "" + +#: ../../content/administration/upgrade.rst:60 +msgid "" +":ref:`Changing hosting type ` (e.g., from on-" +"premise to Odoo Online)" +msgstr "" + +#: ../../content/administration/upgrade.rst:61 +msgid "Migrating from another ERP to Odoo" +msgstr "" + +#: ../../content/administration/upgrade.rst:64 +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:73 +msgid "Upgrading in a nutshell" +msgstr "" + +#: ../../content/administration/upgrade.rst:75 +msgid "" +"Request an upgraded test database (see :ref:`obtaining an upgraded test " +"database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:77 +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:79 +msgid "" +"Thoroughly test the upgraded database (see :ref:`testing the new version of " +"the database `)." +msgstr "" + +#: ../../content/administration/upgrade.rst:81 +msgid "" +"Report any issue encountered during the testing to Odoo by going to the " +"`Support page and selecting \"An issue related to my future upgrade (I am " +"testing an upgrade)\" `_." +msgstr "" + +#: ../../content/administration/upgrade.rst:84 +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:86 +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:88 +msgid "" +"Report any issue encountered during the upgrade to Odoo by going to the " +"`Support page and selecting \"An issue related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:95 +msgid "Obtaining an upgraded test database" +msgstr "" + +#: ../../content/administration/upgrade.rst:97 +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:103 +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:111 +msgid "" +"Odoo Online databases can be manually upgraded via the `database manager " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:114 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "" +"The database manager with an upgrade button next to the name of a database." +msgstr "" + +#: ../../content/administration/upgrade.rst:121 +msgid "" +"Click the **arrow in a circle** icon to start the upgrade process. In the " +"popup, fill in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:123 +msgid "" +"The **version** of Odoo you want to upgrade to, usually the latest version" +msgstr "" + +#: ../../content/administration/upgrade.rst:124 +msgid "" +"The **email** address that should receive the link to the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:125 +msgid "" +"The :guilabel:`Purpose` of the upgrade, which is automatically set to " +":guilabel:`Test` for your first upgrade request" +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "The \"Upgrade your database\" popup." +msgstr "" + +#: ../../content/administration/upgrade.rst:131 +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 "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Clicking the menu arrow displays the upgraded test database." +msgstr "" + +#: ../../content/administration/upgrade.rst:141 +msgid "" +"Odoo.sh is integrated with the upgrade platform to simplify the upgrade " +"process." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "Odoo.sh project and tabs" +msgstr "" + +#: ../../content/administration/upgrade.rst:146 +msgid "" +"The **latest production daily automatic backup** is then sent to the Upgrade" +" platform." +msgstr "" + +#: ../../content/administration/upgrade.rst:148 +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:156 +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:161 +msgid "" +"Check out the :doc:`/developer/howtos/upgrade_custom_db` page for more " +"information." +msgstr "" + +#: ../../content/administration/upgrade.rst:165 +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:173 +msgid "This command has some requirements on the environment it runs in:" +msgstr "" + +#: ../../content/administration/upgrade.rst:175 +msgid "" +"Some external commands that must be provided by the operating system, " +"normally found in any Linux distribution (including WSL). An error will be " +"displayed if one or several of them are missing." +msgstr "" + +#: ../../content/administration/upgrade.rst:178 +msgid "" +"The system user that executes the command needs to be configured with access" +" to the database. Please refer to the PostgreSQL documentation of the " +"`client environment `_ or the `client password file " +"`_ for this " +"requirement." +msgstr "" + +#: ../../content/administration/upgrade.rst:182 +msgid "" +"The script needs to be able to reach one or multiple servers of the upgrade " +"platform both on TCP port 443 and to any random TCP port in the range " +"between 32768 and 60999. This can be in conflict with your restrictive " +"firewall and may need an exception added to the firewall configuration." +msgstr "" + +#: ../../content/administration/upgrade.rst:187 +msgid "" +"The following command can be used to display the general help and the main " +"commands:" +msgstr "" + +#: ../../content/administration/upgrade.rst:193 +msgid "" +"An upgraded test database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:197 +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:202 +msgid "" +"For security reasons, only the person who submitted the upgrade request can " +"download it." +msgstr "" + +#: ../../content/administration/upgrade.rst:203 +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:205 +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:208 +msgid "The upgraded database contains:" +msgstr "" + +#: ../../content/administration/upgrade.rst:210 +msgid "A `dump.sql` file containing the upgraded database" +msgstr "" + +#: ../../content/administration/upgrade.rst:211 +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:218 +msgid "" +"You can request multiple test databases if you wish to test an upgrade more " +"than once." +msgstr "" + +#: ../../content/administration/upgrade.rst:221 +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:229 +msgid "Testing the new version of the database" +msgstr "" + +#: ../../content/administration/upgrade.rst:231 +msgid "" +"It is essential to test 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:236 +msgid "" +"Test databases are neutralized, and some features are disabled to prevent " +"them from impacting the production database:" +msgstr "" + +#: ../../content/administration/upgrade.rst:239 +msgid "Scheduled actions are disabled." +msgstr "" + +#: ../../content/administration/upgrade.rst:240 +msgid "" +"Outgoing mail servers are disabled by archiving the existing ones and adding" +" a fake one." +msgstr "" + +#: ../../content/administration/upgrade.rst:241 +msgid "" +"Payment providers and delivery carriers are reset to the test environment." +msgstr "" + +#: ../../content/administration/upgrade.rst:242 +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:245 +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:248 +msgid "Basic test checklist" +msgstr "" + +#: ../../content/administration/upgrade.rst:250 +msgid "" +"Are there views that are deactivated in your test database but active in " +"your production database?" +msgstr "" + +#: ../../content/administration/upgrade.rst:252 +msgid "Are your usual views still displayed correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:253 +msgid "Are your reports (invoice, sales order, etc.) correctly generated?" +msgstr "" + +#: ../../content/administration/upgrade.rst:254 +msgid "Are your website pages working correctly?" +msgstr "" + +#: ../../content/administration/upgrade.rst:255 +msgid "" +"Are you able to create and modify records? (sales orders, invoices, " +"purchases, users, contacts, companies, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:257 +msgid "Are there any issues with your mail templates?" +msgstr "" + +#: ../../content/administration/upgrade.rst:258 +msgid "Are there any issues with saved translations?" +msgstr "" + +#: ../../content/administration/upgrade.rst:259 +msgid "Are your search filters still present?" +msgstr "" + +#: ../../content/administration/upgrade.rst:260 +msgid "Can you export your data?" +msgstr "" + +#: ../../content/administration/upgrade.rst:264 +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:267 +msgid "Buying this product (Purchase app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:268 +msgid "Confirming the reception of this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:269 +msgid "" +"Checking if the route to receive this product is the same in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:271 +msgid "Selling this product (Sales app) to a random customer." +msgstr "" + +#: ../../content/administration/upgrade.rst:272 +msgid "" +"Opening your customer database (Contacts app), selecting a customer (or " +"company), and checking its data." +msgstr "" + +#: ../../content/administration/upgrade.rst:274 +msgid "Shipping this product (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:275 +msgid "" +"Checking if the route to ship this product is the same as in your production" +" database (Inventory app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:277 +msgid "Validating a customer invoice (Invoicing or Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:278 +msgid "" +"Crediting the invoice (issuing a credit note) and checking if it behaves as " +"in your production database." +msgstr "" + +#: ../../content/administration/upgrade.rst:280 +msgid "Checking your reports' results (Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:281 +msgid "" +"Randomly checking your taxes, currencies, bank accounts, and fiscal year " +"(Accounting app)." +msgstr "" + +#: ../../content/administration/upgrade.rst:282 +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:285 +msgid "" +"This list is **not** exhaustive. Extend the example to your other apps based" +" on your use of Odoo." +msgstr "" + +#: ../../content/administration/upgrade.rst:287 +msgid "" +"If you face an issue while testing your upgraded test database, you can " +"request the assistance of Odoo by going to the `Support page and selecting " +"\"An issue related to my future upgrade (I am testing an 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:293 +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:299 +msgid "Do not forget to test:" +msgstr "" + +#: ../../content/administration/upgrade.rst:301 +msgid "Integrations with external software (EDI, APIs, etc.)" +msgstr "" + +#: ../../content/administration/upgrade.rst:302 +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:304 +msgid "Data exports" +msgstr "" + +#: ../../content/administration/upgrade.rst:305 +msgid "Automated actions" +msgstr "" + +#: ../../content/administration/upgrade.rst:306 +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:312 +msgid "Upgrading the production database" +msgstr "" + +#: ../../content/administration/upgrade.rst:314 +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." +msgstr "" + +#: ../../content/administration/upgrade.rst:317 +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:320 +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:326 +msgid "Going into production without first testing may lead to:" +msgstr "" + +#: ../../content/administration/upgrade.rst:328 +msgid "Users failing to adjust to the changes and new features" +msgstr "" + +#: ../../content/administration/upgrade.rst:329 +msgid "" +"Business interruptions (e.g., no longer having the possibility to validate " +"an action)" +msgstr "" + +#: ../../content/administration/upgrade.rst:330 +msgid "" +"Poor customer experience (e.g., an eCommerce website that does not work " +"correctly)" +msgstr "" + +#: ../../content/administration/upgrade.rst:332 +msgid "" +"The process of upgrading a production database is similar to upgrading a " +"test database, but with a few exceptions." +msgstr "" + +#: ../../content/administration/upgrade.rst:339 +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:344 +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:350 +msgid "" +"The process is similar to :ref:`obtaining an upgraded test database " +"` on the :guilabel:`Production` branch." +msgstr "" + +#: ../../content/administration/upgrade.rst:0 +msgid "View from the upgrade tab" +msgstr "" + +#: ../../content/administration/upgrade.rst:356 +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:362 +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:366 +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:373 +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:380 +msgid "" +"An upgraded production database can also be requested via the `Upgrade page " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:383 +msgid "" +"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:388 +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:392 +msgid "" +"In case of an issue with your production database, you can request the " +"assistance of Odoo by going to the `Support page and selecting \"An issue " +"related to my upgrade (production)\" " +"`_." +msgstr "" + +#: ../../content/administration/upgrade.rst:399 +msgid "Service-level agreement (SLA)" +msgstr "" + +#: ../../content/administration/upgrade.rst:401 +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:404 +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:411 +msgid "Upgrade services covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:413 +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:416 +msgid "the upgrade of all **standard applications**;" +msgstr "" + +#: ../../content/administration/upgrade.rst:417 +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:419 +msgid "" +"the upgrade of all **developments and customizations covered by a " +"maintenance of customizations subscription**." +msgstr "" + +#: ../../content/administration/upgrade.rst:422 +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:428 +msgid "Upgrade services not covered by the SLA" +msgstr "" + +#: ../../content/administration/upgrade.rst:430 +msgid "The following upgrade-related services are **not** included:" +msgstr "" + +#: ../../content/administration/upgrade.rst:432 +msgid "" +"the **cleaning** of pre-existing data and configurations while upgrading;" +msgstr "" + +#: ../../content/administration/upgrade.rst:433 +msgid "" +"the upgrade of **additional modules not covered by a maintenance contract** " +"that are created in-house or by third parties, including Odoo partners; and" +msgstr "" + +#: ../../content/administration/upgrade.rst:435 +msgid "**training** on using the upgraded version's features and workflows." +msgstr "" + +#: ../../content/administration/upgrade.rst:438 +msgid ":doc:`Odoo.sh documentation `" +msgstr "" + +#: ../../content/administration/upgrade.rst:439 +msgid ":doc:`Supported Odoo versions `" +msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/essentials.po b/locale/zh_CN/LC_MESSAGES/essentials.po new file mode 100644 index 0000000000..b2bb187189 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/essentials.po @@ -0,0 +1,4832 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/essentials.rst:3 +msgid "Odoo essentials" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:3 +msgid "Activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:7 +msgid "*Activities* are follow-up tasks tied to a record in an Odoo database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:11 +msgid "" +"The icon used to display activities varies, depending on the :ref:`activity " +"type `:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:14 +msgid "" +":icon:`fa-clock-o` :guilabel:`(clock)` icon: the default activities icon." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:15 +msgid ":icon:`fa-phone` :guilabel:`(phone)` icon: a phone call is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:16 +msgid "" +":icon:`fa-envelope` :guilabel:`(envelope)` icon: an email is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:17 +msgid ":icon:`fa-check` :guilabel:`(check)` icon: a \"to-do\" is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:18 +msgid ":icon:`fa-users` :guilabel:`(people)` icon: a meeting is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:19 +msgid "" +":icon:`fa-upload` :guilabel:`(upload)` icon: a document is scheduled to be " +"uploaded." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:20 +msgid "" +":icon:`fa-pencil-square-o` :guilabel:`(request signature)` icon: a signature" +" request is scheduled." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:23 +msgid "Schedule activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:25 +msgid "" +"Activities can be scheduled on any page of the database that contains a " +":ref:`chatter ` thread, :ref:`Kanban view " +"`, :ref:`list view `, or " +":ref:`activities view ` of an application." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:32 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:34 +msgid "Activities can be created from the chatter on any record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:36 +msgid "" +"To schedule a new activity, click the :guilabel:`Activities` button, located" +" at the top of the chatter. In the :guilabel:`Schedule Activity` pop-up " +"window that appears, :ref:`fill out the Schedule Activity form " +"`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "New activity type form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:47 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:49 +msgid "" +"Activities can also be created from the :icon:`oi-view-kanban` " +":guilabel:`(Kanban)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:51 +msgid "" +"To do so, click on the |clock| located at the bottom of an individual " +"record." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:53 +msgid "" +"Click :guilabel:`+ Schedule An Activity`, then proceed to :ref:`fill out the" +" Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Kanban view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:61 +#: ../../content/applications/essentials/activities.rst:79 +msgid "" +"If a record already has a scheduled activity, the |clock| is replaced by the" +" icon that represents the existing scheduled activity. Click on the activity" +" type's icon to schedule another activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:67 +msgid "List view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:69 +msgid "" +"Activities can also be created from a :icon:`oi-view-list` " +":guilabel:`(list)` view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:71 +msgid "" +"If the :guilabel:`Activities` column is hidden, reveal it using the " +":icon:`oi-settings-adjust` :guilabel:`(settings adjust)` icon in the far-" +"right of the top row." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:74 +msgid "" +"Then, click on the |clock| for the record the activity is being added to, " +"and click :guilabel:`+ Schedule an activity`. Proceed to :ref:`fill out the " +"Schedule Activity form ` that appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "List view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:89 +msgid "Activity view" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:91 +msgid "" +"Most applications in Odoo have an *Activity* view available. If available, a" +" |clock| is visible in the top-right corner of the main menu bar, amongst " +"the other view option icons." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:94 +msgid "To open the activity view, click the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "Top-right menu with the Activities icon called out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:100 +msgid "" +"In this view, all the available activities are listed in the columns, while " +"the horizontal entries represent all the individual records." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:103 +msgid "" +"Activities that appear green have a due date in the future, activities that " +"appear orange are due today, while activities appearing red are overdue." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:106 +msgid "" +"Color bars in each column represent records for specific activity types, and" +" display a number indicating how many activities are scheduled for that " +"type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:109 +msgid "" +"If multiple activity types are scheduled for a record, a number appears in " +"the box, indicating the total number of scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:113 +msgid "" +"Activity colors, and their relation to an activity's due date, are " +"consistent throughout Odoo, regardless of the activity type, or the view." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:116 +msgid "" +"To schedule an activity for a record, hover over the corresponding field. " +"Click the :icon:`fa-plus` :guilabel:`(plus)` icon that appears, and then " +":ref:`fill out the Schedule Activity form `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity view of the CRM pipeline and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:127 +msgid "Schedule Activity form" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:129 +msgid "" +"Activities can be scheduled from many different places, such as from the " +":ref:`chatter ` of a record, or from one of multiple " +"views in an application, when available: the :ref:`Kanban view " +"`, :ref:`list view `, or :ref:`activity " +"view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:134 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:136 +msgid "" +":guilabel:`Activity Type`: select the type of activity from the drop-down " +"menu. The default options are: :guilabel:`Email`, :guilabel:`Call`, " +":guilabel:`Meeting`, or :guilabel:`To-Do`. Depending on what other " +"applications are installed, additional options may be available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:139 +msgid "" +":guilabel:`Summary`: enter a short title for the activity, such as `Discuss " +"Proposal`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:140 +msgid "" +":guilabel:`Due Date`: using the calendar popover, select the activity's " +"deadline." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:141 +msgid "" +":guilabel:`Assigned to`: by default, the current user populates this field. " +"To assign a different user to the activity, select them from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:143 +msgid "" +":guilabel:`Notes`: add any additional information for the activity in this " +"field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:145 +msgid "" +"When the :guilabel:`Schedule Activity` pop-up window is completed, click one" +" of the following buttons:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:148 +msgid "" +":guilabel:`Open Calendar`: opens the user's calendar to add and schedule the" +" activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:150 +msgid "" +"Click on the desired date and time for the activity, and a :guilabel:`New " +"Event` pop-up window appears. The summary from the *Schedule Activity* pop-" +"up window populates the :guilabel:`Title` field." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:154 +msgid "" +"Enter the information in the :guilabel:`New Event` pop-up window, then click" +" :guilabel:`Save & Close` to schedule it. Once scheduled, the activity is " +"added to the chatter under the :guilabel:`Planned Activities` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:159 +msgid "" +"The :guilabel:`Open Calendar` button **only** appears if the " +":guilabel:`Activity Type` is set to either :guilabel:`Call` or " +":guilabel:`Meeting`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:162 +msgid "" +":guilabel:`Schedule`: schedules the activity, and adds the activity to the " +"chatter under :guilabel:`Planned Activities`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:164 +msgid "" +":guilabel:`Schedule & Mark as Done`: adds the details of the activity to the" +" chatter under :guilabel:`Today`. The activity is not scheduled, and is " +"automatically marked as done." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:166 +msgid "" +":guilabel:`Done & Schedule Next`: adds the details of the activity to the " +"chatter under :guilabel:`Today`. The activity is not scheduled, is " +"automatically marked as done, and a new :guilabel:`Schedule Activity` pop-up" +" window appears." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:169 +msgid "" +":guilabel:`Cancel`: discards any changes made on the :guilabel:`Schedule " +"Activity` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "View of CRM leads and the option to schedule an activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:178 +msgid "All scheduled activities" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:180 +msgid "" +"To view a consolidated list of activities, organized by application, click " +"the |clock| in the header menu, located in the top-right corner." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:183 +msgid "" +"If any activities are scheduled, the number of activities appear in a red " +"bubble on the |clock|." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:186 +msgid "" +"All activities for each application are further divided into subsections, " +"indicating where in the application the activity is to be completed. Each " +"sub-section lists the number of scheduled activities that are " +":guilabel:`Late`, due :guilabel:`Today`, and scheduled in the " +":guilabel:`Future`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:192 +msgid "" +"In the *Time Off* application, one activity is scheduled to be done in the " +"*All Time Off* requests dashboard, and six activities are scheduled to be " +"done in the *Allocations* dashboard." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:195 +msgid "" +"These requests appear in two separate lists in the all activities drop-down " +"menu: one labeled `Time Off` and one labeled `Time Off Allocation`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:0 +msgid "" +"The list of activities that is accessed from the main menu bar. Two entries for the Time\n" +"Off application are highlighted." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:204 +msgid "" +"The option to :ref:`Request a Document ` is available at " +"the bottom of the list of all scheduled activities." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:210 +msgid "Activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:212 +msgid "" +"To view the currently configured types of activities in the database, " +"navigate to :menuselection:`Settings app --> Discuss section --> Activities " +"setting --> Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "" +"Activity Types button in the Settings application under the Discuss section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:219 +msgid "" +"Doing so reveals the :guilabel:`Activity Types` page, where the existing " +"activity types are found." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:222 +msgid "" +"Individual applications have a list of *Activity Types* dedicated to that " +"application. For example, to view and edit the activities available for the " +"*CRM* application, go to :menuselection:`CRM app --> Configuration --> " +"Activity Types`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "The list of activity types already configured and available." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:231 +msgid "Edit activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:233 +msgid "" +"To edit an existing :ref:`activity type `, click on the " +"activity type, and the activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:236 +msgid "" +"Make any desired changes to the activity type form. The form automatically " +"saves, but it can be saved manually at any time by clicking the " +":guilabel:`Save Manually` option, represented by a :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon, located in the top-left corner of the page." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:241 +msgid "Create new activity types" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:243 +msgid "" +"To create a new :ref:`activity type `, click " +":guilabel:`New` from the :guilabel:`Activity Types` page, and a blank " +"activity type form loads." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:246 +msgid "" +"Enter a :guilabel:`Name` for the activity type at the top of the form, then " +"enter the following information on the form." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:250 +msgid "Activity Settings section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:252 +msgid "" +":guilabel:`Action`: Using the drop-down menu, select an action associated " +"with this new activity type. Some actions trigger specific behaviors after " +"an activity is scheduled, such as:" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:255 +msgid "" +":guilabel:`Upload Document`: If selected, a link to upload a document is " +"automatically added to the planned activity in the chatter." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:257 +msgid "" +":guilabel:`Call` or :guilabel:`Meeting`: If selected, users have the option " +"to open their calendar to select a date and time for the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:259 +msgid "" +":guilabel:`Request Signature`: If selected, a link to open a signature " +"request pop-up window is automatically added to the planned activity in the " +"chatter. This requires the Odoo *Sign* application to be installed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:264 +msgid "" +"Available activity types vary based on the installed applications in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:266 +msgid "" +":guilabel:`Folder`: Select a specific :ref:`folder ` to " +"save a document to. This field **only** appears if :guilabel:`Upload " +"Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:269 +msgid "" +":guilabel:`Default User`: Select a user from the drop-down menu to " +"automatically assign this activity to the selected user when this activity " +"type is scheduled. If this field is left blank, the activity is assigned to " +"the user who creates the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:272 +msgid "" +":guilabel:`Default Summary`: enter a note to include whenever this activity " +"type is created." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:275 +msgid "" +"The information in the :guilabel:`Default User` and :guilabel:`Default " +"Summary` fields are included when an activity is created. However, they can " +"be altered before the activity is scheduled or saved." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:279 +msgid "" +":guilabel:`Keep Done`: Tick this checkbox to keep activities that have been " +"marked as `Done` visible in the :ref:`activity view `." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:281 +msgid ":guilabel:`Default Note`: enter any notes to appear with the activity." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:284 +msgid "Next Activity section" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:286 +msgid "" +"It is possible to have another activity either suggested or triggered. To do" +" so, configure the :guilabel:`Next Activity` section." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:289 +msgid "" +":guilabel:`Chaining Type`: select either :guilabel:`Suggest Next Activity` " +"or :guilabel:`Trigger Next Activity` from the drop-down menu. Depending on " +"the selected option, either the :guilabel:`Suggest` or :guilabel:`Trigger` " +"field is displayed." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:294 +msgid "" +"The :guilabel:`Chaining Type` field does **not** appear if :guilabel:`Upload" +" Document` is selected for the :guilabel:`Action`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:297 +msgid "" +":guilabel:`Suggest/Trigger`: depending on what is selected for the " +":guilabel:`Chaining Type`, this field either displays :guilabel:`Suggest` or" +" :guilabel:`Trigger`. Using the drop-down menu, select the activity to " +"recommend or schedule as a follow-up task to the activity type." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:300 +msgid "" +":guilabel:`Schedule`: configure when the next activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:302 +msgid "" +"First, enter a numerical value indicating when the activity is suggested or " +"triggered." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:304 +msgid "" +"Next to this field, a :guilabel:`Days` field is visible. Click " +":guilabel:`Days`, the default option, to reveal a drop-down menu. Select the" +" desired time-frame option from the list. The options are :guilabel:`Days`, " +":guilabel:`Weeks`, or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:308 +msgid "" +"Lastly, using the drop-down menu, select whether the activity is scheduled " +"or triggered either :guilabel:`after previous activity deadline` or " +":guilabel:`after completion date`." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:-1 +msgid "A new Activity form with all the fields filled out." +msgstr "" + +#: ../../content/applications/essentials/activities.rst:316 +msgid ":doc:`../productivity/discuss`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:317 +msgid ":doc:`../productivity/discuss/team_communication`" +msgstr "" + +#: ../../content/applications/essentials/activities.rst:318 +msgid ":doc:`../sales/crm/optimize/utilize_activities`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:5 +msgid "Contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:7 +msgid "" +"Contacts are created in the **Contacts** application for customers the " +"company does business with through Odoo. A contact is a repository of vital " +"business information, facilitating communication and business transactions." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:12 +msgid "Contact form" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:14 +msgid "" +"To create a new contact, navigate to the :menuselection:`Contacts app`, and " +"click :guilabel:`Create`. A new form appears where various contact " +"information can be added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:18 +msgid "Contact type" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:20 +msgid "" +"Odoo allows for both :guilabel:`Individual` and :guilabel:`Company` " +"contacts. Select either :guilabel:`Individual` or :guilabel:`Company`, " +"depending on the type of contact that is being added." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:24 +msgid "Name" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:26 +msgid "" +"First, fill in the name of the :guilabel:`Individual` or " +":guilabel:`Company`. This is how the name appears throughout the database. " +"This field is **mandatory**." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:30 +msgid "" +":guilabel:`Individual` contacts can have a :guilabel:`Company` contact " +"linked to it. After selecting :guilabel:`Individual`, a new " +":guilabel:`Company Name...` field appears below the first name field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:35 +msgid "Address" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:37 +msgid "" +"Next, enter the :guilabel:`Address` of the :guilabel:`Company` or " +":guilabel:`Individual`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:40 +msgid "" +"If the :guilabel:`Individual` option is chosen, then the *type of address* " +"can be chosen from a drop-down menu. Options for this drop-down menu " +"include: :guilabel:`Contact`, :guilabel:`Invoice Address`, " +":guilabel:`Delivery Address`, :guilabel:`Other Address`, and " +":guilabel:`Private Address`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:46 +msgid "Additional fields" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:48 +msgid "" +"Additional details are included on the initial form. The following fields " +"are available:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:50 +msgid ":guilabel:`VAT`: Value Added Tax number." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:51 +msgid "" +":guilabel:`Citizen Identification`: citizen or government identification " +"number (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:53 +msgid "" +":guilabel:`Job Position`: list the job position of the " +":guilabel:`Individual` (only available on :guilabel:`Individual`)." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:55 +msgid "" +":guilabel:`Phone`: list phone number (with country code). Make a call, send " +"an SMS, or WhatsApp message by hovering over the field on the saved form, " +"and clicking the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:57 +msgid "" +":guilabel:`Mobile`: list mobile phone number (with country code). Make a " +"call, send an SMS, or WhatsApp message by hovering over the field on the " +"saved form, and clicking on the desired option." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:59 +msgid ":guilabel:`Email`: enter the email address with the domain." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:60 +msgid "" +":guilabel:`Website`: enter the full website address, starting with `http` or" +" `https`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:61 +msgid "" +":guilabel:`Title`: select :guilabel:`Doctor`, :guilabel:`Madam`, " +":guilabel:`Miss`, :guilabel:`Mister`, :guilabel:`Professor`, or create a new" +" one directly from this field." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:63 +msgid "" +":guilabel:`Tags`: enter preconfigured tags by typing them in the field, or " +"clicking the drop-down menu, and selecting one. To create a new one, type " +"the new tag in the field, and click :guilabel:`Create` from the resulting " +"drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:68 +msgid "Contacts & Addresses tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:70 +msgid "" +"At the bottom of the contact form are several tabs. On the " +":guilabel:`Contacts & Addresses` tab, contacts can be added that are " +"associated with a :guilabel:`Company` and related addresses. For example, a " +"specific contact person for the company can be listed here." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:74 +msgid "" +"Multiple addresses can be added on both :guilabel:`Individual` and " +":guilabel:`Company` contacts. To do so, click :guilabel:`Add` in the " +":guilabel:`Contacts & Addresses` tab. Doing so reveals a :guilabel:`Create " +"Contact` pop-up form, in which additional addresses can be configured." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Add a contact/address to the contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:82 +msgid "" +"On the :guilabel:`Create Contact` pop-up form, start by clicking the default" +" :guilabel:`Other Address` field at the top to reveal a drop-down menu of " +"address-related options." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:85 +msgid "Select any of the following options:" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:87 +msgid "" +":guilabel:`Contact`: adds another contact to the existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:88 +msgid "" +":guilabel:`Invoice Address`: adds a specific invoice address to the existing" +" contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:89 +msgid "" +":guilabel:`Delivery Address`: adds a specific delivery address to the " +"existing contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:90 +msgid "" +":guilabel:`Other Address`: adds an alternate address to the existing contact" +" form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:91 +msgid "" +":guilabel:`Private Address`: adds a private address to the existing contact " +"form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:-1 +msgid "Create a new contact/address on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:97 +msgid "" +"Once an option is selected, enter the corresponding contact information that" +" should be used for the specified address type." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:100 +msgid "" +"Add the :guilabel:`Contact Name`, :guilabel:`Address`, :guilabel:`Email`, " +"along with the :guilabel:`Phone` and/or :guilabel:`Mobile` numbers below." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:103 +msgid "" +"Set the :guilabel:`Job Position`, which appears if the :guilabel:`Contact` " +"address type has been selected. This is similar to the " +":guilabel:`Individual` contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:106 +msgid "" +"To add a note, click on the text field next to :guilabel:`Notes`, and write " +"anything that is applicable to the customer or contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:109 +msgid "" +"Then, click :guilabel:`Save & Close` to save the address, and close the " +":guilabel:`Create Contact` window. Or, click :guilabel:`Save & New` to save " +"the address, and immediately input another one." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:113 +msgid "Sales & Purchase tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:115 +msgid "" +"Next, is the :guilabel:`Sales & Purchases` tab, which only appears when the " +"*Sales*, *Purchase*, **or** *Point of Sale* applications are installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:118 +msgid "" +"The :guilabel:`Fiscal Position` can be set on the :guilabel:`Sales & " +"Purchases` tab. Select a :guilabel:`Fiscal Position` from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:122 +msgid "Sales section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:124 +msgid "" +"Under the :guilabel:`Sales` heading, a specific :guilabel:`Salesperson` can " +"be assigned to a contact. To do that, click the :guilabel:`Salesperson` " +"drop-down field, and select one. Create a new :guilabel:`Salesperson` by " +"typing the user's name, and making the appropriate selection." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:128 +msgid "" +"Certain :guilabel:`Payment Terms`, or a certain :guilabel:`Pricelist`, can " +"also be set, if needed. Click the drop-down menu next to :guilabel:`Payment " +"Terms`, and change it to one of the preselected :guilabel:`Payment Terms`, " +"or :guilabel:`Create` a new one. Select the :guilabel:`Pricelist` drop-down " +"menu to choose the appropriate :guilabel:`Pricelist`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:133 +msgid "" +"Click into the :guilabel:`Delivery Method` field to select an option from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:136 +msgid "Point Of Sale section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:138 +msgid "" +"Under the :guilabel:`Point Of Sale` heading, enter a :guilabel:`Barcode` " +"that can be used to identify the contact. Use the :guilabel:`Loyalty Points`" +" field to track points the user won as part of a *Loyalty Program*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:143 +msgid "Purchase section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:145 +msgid "" +"Specify :guilabel:`Payment Terms`, :guilabel:`1099 Box` information, and a " +"preferred :guilabel:`Payment Method` here. A :guilabel:`Receipt Reminder` " +"can be set here, as well." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:149 +msgid "Misc section" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:151 +msgid "" +"Under the :guilabel:`Misc.` heading, use :guilabel:`Reference` field to add " +"any additional information for this contact. If this contact should only be " +"accessible for one company in a multi-company database, select it from the " +":guilabel:`Company` field drop-down list. Use the :guilabel:`Website` drop-" +"down menu to restrict the publishing of this contact to one website (if " +"working on a database with multiple websites). Select one or more " +":guilabel:`Website Tags` to assist in filtering published customers on the " +"`/customers` website page. Select an :guilabel:`Industry` for this contact " +"from the drop-down menu. Use the :guilabel:`SLA Policies` field to assign a " +"*Helpdesk* SLA policy to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:161 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:163 +msgid "" +"The :guilabel:`Accounting` tab appears when the *Accounting* application is " +"installed. Here, a user can add any related :guilabel:`Bank Accounts`, or " +"set default :guilabel:`Accounting entries`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:166 +msgid "" +"Under the :guilabel:`Miscellaneous` heading, use the :guilabel:`LEI` field " +"to enter a Legal Entity Identifier, if necessary." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:170 +msgid "Internal Notes tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:172 +msgid "" +"Following the :guilabel:`Accounting` tab is the :guilabel:`Internal Notes` " +"tab, where notes can be left on this contact form, just like on the contact " +"form noted above." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:176 +msgid "Partner Assignment tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:178 +msgid "" +"Next is the :guilabel:`Partner Assignment` tab, which by default, includes a" +" :guilabel:`Geolocation` section, and other partner options, including " +":guilabel:`Partner Activation` and :guilabel:`Partner Review` " +"configurations. These are **only** present when the *Resellers* module is " +"installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:183 +msgid "" +"Follow the :doc:`Resellers documentation " +"<../sales/crm/track_leads/resellers>` for more information on publishing " +"partners on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:187 +msgid "Membership tab" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:189 +msgid "" +"Finally, there is the :guilabel:`Membership` tab on contact forms, which can" +" help users manage any memberships that are being offered to this specific " +"contact. It should be noted that this tab **only** appears when the " +"*Members* application is installed." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:194 +msgid "Activate membership" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:196 +msgid "" +"To activate a contact's membership, click :guilabel:`Buy Membership` in the " +":guilabel:`Membership` tab of a contact form. On the pop-up window that " +"appears, select a :guilabel:`Membership` from the drop-down menu. Then, " +"configure a :guilabel:`Member Price`. Click :guilabel:`Invoice Membership` " +"when both fields are filled in." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:201 +msgid "" +"Alternatively, to offer a free membership, tick the :guilabel:`Free Member` " +"checkbox, in the :guilabel:`Membership` tab of a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:205 +msgid "" +"Follow the :doc:`Members documentation <../sales/members>` for more " +"information on publishing members on the website." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:209 +msgid "Smart buttons" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:211 +msgid "" +"At the top of the contact form, there are some additional options available," +" known as *smart buttons*." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:214 +msgid "" +"Here, Odoo displays a variety of records, related to this contact, that were" +" created on other apps. Odoo integrates information from every single app, " +"so there are many smart buttons." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:218 +msgid "" +"For example, there is an :guilabel:`Opportunities` smart button, where all " +"the opportunities related to this customer from the *CRM* app are " +"accessible." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:222 +msgid "" +"If the corresponding applications are installed, their related smart buttons" +" appear automatically on a contact form." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:225 +msgid "" +"A user can see any :guilabel:`Meetings`, :guilabel:`Sales`, :guilabel:`POS " +"Orders`, :guilabel:`Subscriptions`, project :guilabel:`Tasks`, and the " +":guilabel:`More` smart button reveals additional options, via a drop-down " +"menu. A user can even quickly access :guilabel:`Purchases`, " +":guilabel:`Helpdesk` tasks, :guilabel:`On-time Rate` for deliveries, " +":guilabel:`Invoiced` information, :guilabel:`Vendor Bills`, and the " +":guilabel:`Partner Ledger` connected to this contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:231 +msgid "" +"Deliveries, documents, loyalty cards, and direct debits are *also* linked to" +" smart buttons, like this, should there be any outstanding/on-file for this " +"contact." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:234 +msgid "" +"If the contact is a partner, the user can visit their partner page on the " +"Odoo-built website by clicking the :guilabel:`Go to Website` smart button." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:238 +msgid "Archive contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:240 +msgid "" +"If a user decides they no longer want to have this contact active, the " +"record can be archived. To do that, go to the :icon:`fa-cog` " +":guilabel:`Action` menu at the top of the contact form, and click " +":guilabel:`Archive`." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:244 +msgid "" +"Then, click :guilabel:`OK` from the resulting :guilabel:`Confirmation` pop-" +"up window." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:246 +msgid "" +"With this contact successfully archived, as indicated by a banner at the " +"top, they do not show up in the main contacts page, but they can still be " +"searched for with the :guilabel:`Archived` filter." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:250 +msgid "" +"A contact can be *unarchived*, if the user decides to work with them again. " +"To do that, just click the :icon:`fa-cog` :guilabel:`Action` menu again at " +"the top of the archived contact form, and click :guilabel:`Unarchive`. Upon " +"doing so, the :guilabel:`Archived` banner is removed, and the contact is " +"restored." +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:256 +msgid "" +":doc:`Add different addresses in CRM " +"<../sales/sales/sales_quotations/different_addresses>`" +msgstr "" + +#: ../../content/applications/essentials/contacts.rst:257 +msgid "" +"`Odoo's eLearning Contacts tutorial " +"`_" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:3 +msgid "Merge contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:5 +msgid "" +"Odoo's *Contacts* application allows user's to merge duplicate contacts, " +"without losing any information in the process. This keeps the database " +"organized, and prevents contacts from being contacted by more than one " +"salesperson." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:12 +msgid "Merge duplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:15 +msgid "" +"Merging is an irreversible action. Do **not** merge contacts unless " +"absolutely certain they should be combined." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:18 +msgid "" +"Navigate to the :menuselection:`Contacts app`, and select the :icon:`oi-" +"view-list` :guilabel:`(list)` icon. Select two or more duplicate contacts " +"from the list, and tick the checkbox (on the far-left) for the contacts that" +" should be merged. Then, click the :icon:`fa-cog` :guilabel:`Actions` icon, " +"and select :guilabel:`Merge` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge contacts option in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:27 +msgid "" +"This opens the :guilabel:`Merge` pop-up window. From here, review the " +"details of the contacts before confirming they should be merged. If any " +"contacts in the list should **not** be merged, click the :icon:`fa-times` " +":guilabel:`(delete)` icon at the far right of the contact." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:32 +msgid "" +"Click the individual contact to open the record for that contact, and view " +"additional information." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:-1 +msgid "The merge pop-up window in the Contacts application." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:39 +msgid "" +"Click the :guilabel:`Destination Contact` field, and select an option from " +"the drop-down list. This field defaults to the contact record that was " +"created first in the system." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:42 +msgid "" +"After confirming the information on the pop-up window, click " +":guilabel:`Merge Contacts`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:45 +msgid "Deduplicate contacts" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:47 +msgid "" +"After the merge is finished, a pop-up window appears confirming it is " +"complete. This pop-up window also contains a :guilabel:`Deduplicate the " +"other Contacts` button. This feature searches for duplicated records, based " +"on selected criteria, and merges them automatically, or after manual " +"approval." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:52 +msgid "" +"Click the :guilabel:`Deduplicate the other Contacts` button to open the " +":guilabel:`Deduplicate Contacts` pop-up window." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:55 +msgid "" +"Select one or more fields to be used in the search for duplicated records. " +"Duplicated contacts can be searched, based on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:58 +msgid ":guilabel:`Email`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:59 +msgid ":guilabel:`Name`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:60 +msgid ":guilabel:`Is Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:61 +msgid ":guilabel:`VAT`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:62 +msgid ":guilabel:`Parent Company`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:65 +msgid "" +"If more than one field is selected, only records that have **all** fields in" +" common are suggested as duplicates." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:68 +msgid "" +"If necessary, select criteria to be used to exclude potential duplicates " +"from the search. Potential duplicates can be excluded from the search, based" +" on the following criteria:" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:71 +msgid ":guilabel:`A user associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:72 +msgid ":guilabel:`Journal Items associated to the contact`" +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:74 +msgid "" +"After confirming the search criteria, click either :guilabel:`Merge with " +"Manual Check`, :guilabel:`Merge Automatically`, or :guilabel:`Merge " +"Automatically all process`." +msgstr "" + +#: ../../content/applications/essentials/contacts/merge.rst:77 +msgid "" +"If :guilabel:`Merge with Manual Check` is selected, complete the merge by " +"following the :ref:`steps above `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:3 +msgid "Export and import data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:8 +msgid "" +"In Odoo, it is sometimes necessary to export or import data for running " +"reports, or for data modification. This document covers the export and " +"import of data into and out of Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:12 +msgid "" +"Sometimes, users run into a 'time out' error, or a record does not process, " +"due to its size. This can occur with large exports, or in cases where the " +"import file is too large. To circumvent this limitation surrounding the size" +" of the records, process exports or imports in smaller batches." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:19 +msgid "Export data from Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:21 +msgid "" +"When working with a database, it is sometimes necessary to export data in a " +"distinct file. Doing so can aid in reporting on activities, although, Odoo " +"provides a precise and easy reporting tool with each available application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:25 +msgid "" +"With Odoo, the values can be exported from any field in any record. To do " +"so, activate the list view (|list|), on the items that need to be exported, " +"then select the records that should be exported. To select a record, tick " +"the checkbox next to the corresponding record. Finally, click on |actions|, " +"then :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "View of the different things to enable/click to export data." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:33 +msgid "" +"When clicking on :guilabel:`Export`, an :guilabel:`Export Data` pop-over " +"window appears, with several options for the data to export:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Overview of options to consider when exporting data in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:39 +msgid "" +"With the :guilabel:`I want to update data (import-compatable export)` option" +" ticked, the system only shows the fields that can be imported. This is " +"helpful in the case where the :ref:`existing records need to be updated " +"`. This works like a filter. Leaving the box " +"unticked, gives many more field options because it shows all the fields, not" +" just the ones that can be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:44 +msgid "" +"When exporting, there is the option to export in two formats: `.csv` and " +"`.xls`. With `.csv`, items are separated by a comma, while `.xls` holds " +"information about all the worksheets in a file, including both content and " +"formatting." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:47 +msgid "" +"These are the items that can be exported. Use the :guilabel:`> (right " +"arrow)` icon to display more sub-field options. Use the :guilabel:`Search` " +"bar to find specific fields. To use the :guilabel:`Search` option more " +"efficiently, click on all the :guilabel:`> (right arrows)` to display all " +"fields." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:51 +msgid "" +"The :guilabel:`+ (plus sign)` icon button is present to add fields to the " +":guilabel:`Fields to export` list." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:53 +msgid "" +"The :guilabel:`↕️ (up-down arrow)` to the left of the selected fields can be" +" used to move the fields up and down, to change the order in which they are " +"displayed in the exported file. Drag-and-drop using the :guilabel:`↕️ (up-" +"down arrow)` icon." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:56 +msgid "" +"The :guilabel:`🗑️ (trash can)` icon is used to remove fields. Click on the " +":guilabel:`🗑️ (trash can)` icon to remove the field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:58 +msgid "" +"For recurring reports, it is helpful to save export presets. Select all the " +"needed fields, and click on the template drop-down menu. Once there, click " +"on :guilabel:`New template`, and give a unique name to the export just " +"created. Click the :guilabel:`💾 (floppy drive)` icon to save the " +"configuration. The next time the same list needs to be exported, select the " +"related template that was previously saved from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:65 +msgid "" +"It is helpful to know the field's external identifier. For example, " +":guilabel:`Related Company` in the export user interface is equal to " +"*parent_id* (external identifier). This is helpful because then, the only " +"data exported is what should be modified and re-imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:72 +msgid "Import data into Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:74 +msgid "" +"Importing data into Odoo is extremely helpful during implementation, or in " +"times where data needs to be :ref:`updated in bulk `. The following documentation covers how to import data into an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:79 +msgid "" +"Imports are permanent and **cannot** be undone. However, it is possible to " +"use filters (`created on` or `last modified`) to identify records changed or" +" created by the import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:83 +msgid "" +"Activating :ref:`developer mode ` changes the visible import" +" settings in the left menu. Doing so reveals an :menuselection:`Advanced` " +"menu. Included in this advanced menu are two options: :guilabel:`Track " +"history during import` and :guilabel:`Allow matching with subfields`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Advanced import options when developer mode is activated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:90 +msgid "" +"If the model uses openchatter, the :guilabel:`Track history during import` " +"option sets up subscriptions and sends notifications during the import, but " +"leads to a slower import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:93 +msgid "" +"Should the :guilabel:`Allow matching with subfields` option be selected, " +"then all subfields within a field are used to match under the " +":guilabel:`Odoo Field` while importing." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:99 +msgid "Get started" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:101 +msgid "" +"Data can be imported on any Odoo business object using either Excel " +"(`.xlsx`) or :abbr:`CSV (Comma-separated Values)` (`.csv`) formats. This " +"includes: contacts, products, bank statements, journal entries, and orders." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:105 +msgid "" +"Open the view of the object to which the data should be imported/populated, " +"click the :icon:`fa-cog` (:guilabel:`gear`) icon and select " +":guilabel:`Import records`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Action menu revealed with the import records option highlighted." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:111 +msgid "" +"Click :icon:`fa-download`:guilabel:`Import Template for Customers` at the " +"center of the page to download a :ref:`template " +"` and populate it with the " +"company's own data. Such templates can be imported in one click since the " +"data mapping is already preconfigured." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:116 +msgid "" +"To upload the downloaded template or your own file, follow the next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:118 +msgid "Click :guilabel:`Upload Data File` and select the desired file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:119 +msgid "" +"Adjust the :guilabel:`Formatting` options as needed (for CSV files only)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:120 +msgid "" +"Ensure all data in the :guilabel:`File Column` is correctly mapped to the " +"appropriate :guilabel:`Odoo Field` and free of errors." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:122 +msgid "" +"(Optional) Click :guilabel:`Load Data File` to reload the same file or " +"upload a different one." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:123 +msgid "Click :guilabel:`Test` to verify that the data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:124 +msgid "Click :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:127 +msgid "" +"The :guilabel:`Formatting` options do **not** appear when importing the " +"proprietary Excel file type (i.e., `.xls` or `.xlsx`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:133 +msgid "Adapt a template" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:135 +msgid "" +"Import templates are provided in the import tool of the most common data to " +"import (contacts, products, bank statements, etc.). Open them with any " +"spreadsheet software (*Microsoft Office*, *OpenOffice*, *Google Drive*, " +"etc.)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:139 +msgid "Once the template is downloaded, proceed to follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:141 +msgid "Add, remove, and sort columns to best fit the data structure." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:142 +msgid "" +"It is strongly advised to **not** remove the :guilabel:`External ID` (ID) " +"column (see why in the next section)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:144 +msgid "" +"Set a unique ID to every record by dragging down the ID sequencing in the " +":guilabel:`External ID` (ID) column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "" +"An animation of the mouse dragging down the ID column, so each record has a " +"unique ID." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:151 +msgid "" +"When a new column is added, Odoo may not be able to map it automatically, if" +" its label does not fit any field within Odoo. However, new columns can be " +"mapped manually when the import is tested. Search the drop-down menu for the" +" corresponding field." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Drop-down menu expanded in the initial import screen on Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:158 +msgid "" +"Then, use this field's label in the import file to ensure future imports are" +" successful." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:161 +msgid "" +"Another useful way to find out the proper column names to import is to " +"export a sample file using the fields that should be imported. This way, if " +"there is not a sample import template, the names are accurate." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:169 +msgid "Import from another application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:171 +msgid "" +"The :guilabel:`External ID` (ID) is a unique identifier for the line item. " +"Feel free to use one from previous software to facilitate the transition to " +"Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:174 +msgid "" +"Setting an ID is not mandatory when importing, but it helps in many cases:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:176 +msgid "" +":ref:`Update imports `: import the same file several" +" times without creating duplicates." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:178 +msgid ":ref:`Import relation fields `." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:180 +msgid "" +"To recreate relationships between different records, the unique identifier " +"from the original application should be used to map it to the " +":guilabel:`External ID` (ID) column in Odoo." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:183 +msgid "" +"When another record is imported that links to the first one, use **XXX/ID** " +"(XXX/External ID) for the original unique identifier. This record can also " +"be found using its name." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:187 +msgid "" +"It should be noted that conflicts occur if two (or more) records have the " +"same *External ID*." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:190 +msgid "Field missing to map column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:192 +msgid "" +"Odoo heuristically tries to find the type of field for each column inside " +"the imported file, based on the first ten lines of the files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:195 +msgid "" +"For example, if there is a column only containing numbers, only the fields " +"with the *integer* type are presented as options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:198 +msgid "" +"While this behavior might be beneficial in most cases, it is also possible " +"that it could fail, or the column may be mapped to a field that is not " +"proposed by default." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:201 +msgid "" +"If this happens, check the :guilabel:`Show fields of relation fields " +"(advanced) option`, then a complete list of fields becomes available for " +"each column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:-1 +msgid "Searching for the field to match the tax column." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:208 +msgid "Change data import format" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:211 +msgid "" +"Odoo can automatically detect if a column is a date, and tries to guess the " +"date format from a set of most commonly used date formats. While this " +"process can work for many date formats, some date formats are not " +"recognizable. This can cause confusion, due to day-month inversions; it is " +"difficult to guess which part of a date format is the day, and which part is" +" the month, in a date, such as `01-03-2016`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:217 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, Odoo provides " +":guilabel:`Formatting` options." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:220 +msgid "" +"To view which date format Odoo has found from the file, check the " +":guilabel:`Date Format` that is shown when clicking on options under the " +"file selector. If this format is incorrect, change it to the preferred " +"format using *ISO 8601* to define the format." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:225 +msgid "" +"*ISO 8601* is an international standard, covering the worldwide exchange, " +"along with the communication of date and time-related data. For example, the" +" date format should be `YYYY-MM-DD`. So, in the case of July 24th 1981, it " +"should be written as `1981-07-24`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:230 +msgid "" +"When importing Excel files (`.xls`, `.xlsx`), consider using *date cells* to" +" store dates. This maintains locale date formats for display, regardless of " +"how the date is formatted in Odoo. When importing a :abbr:`CSV (Comma-" +"separated Values)` file, use Odoo's :guilabel:`Formatting` section to select" +" the date format columns to import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:236 +msgid "Import numbers with currency signs" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:238 +msgid "" +"Odoo fully supports numbers with parenthesis to represent negative signs, as" +" well as numbers with currency signs attached to them. Odoo also " +"automatically detects which thousand/decimal separator is used. If a " +"currency symbol unknown to Odoo is used, it might not be recognized as a " +"number, and the import crashes." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:244 +msgid "" +"When importing a :abbr:`CSV (Comma-separated Values)` file, the " +":guilabel:`Formatting` menu appears on the left-hand column. Under these " +"options, the :guilabel:`Thousands Separator` can be changed." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:248 +msgid "" +"Examples of supported numbers (using 'thirty-two thousand' as the figure):" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:250 +msgid "32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:251 +msgid "32000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:252 +msgid "32,000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:253 +msgid "-32000.00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:254 +msgid "(32000.00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:255 +msgid "$ 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:256 +msgid "(32000.00 €)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:258 +msgid "Example that will not work:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:260 +msgid "ABC 32.000,00" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:261 +msgid "$ (32.000,00)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:264 +msgid "" +"A :guilabel:`() (parenthesis)` around the number indicates that the number " +"is a negative value. The currency symbol **must** be placed within the " +"parenthesis for Odoo to recognize it as a negative currency value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:269 +msgid "Import preview table not displayed correctly" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:271 +msgid "" +"By default, the import preview is set on commas as field separators, and " +"quotation marks as text delimiters. If the :abbr:`CSV (Comma-separated " +"Values)` file does not have these settings, modify the " +":guilabel:`Formatting` options (displayed under the :guilabel:`Import` " +":abbr:`CSV (Comma-separated Values)` file bar after selecting the :abbr:`CSV" +" (Comma-separated Values)` file)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:277 +msgid "" +"If the :abbr:`CSV (Comma-separated Values)` file has a tabulation as a " +"separator, Odoo does **not** detect the separations. The file format options" +" need to be modified in the spreadsheet application. See the following " +":ref:`Change CSV file format ` section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:285 +msgid "Change CSV file format in spreadsheet application" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:287 +msgid "" +"When editing and saving :abbr:`CSV (Comma-separated Values)` files in " +"spreadsheet applications, the computer's regional settings are applied for " +"the separator and delimiter. Odoo suggests using *OpenOffice* or " +"*LibreOffice*, as both applications allow modifications of all three options" +" (from *LibreOffice* application, go to :menuselection:`'Save As' dialog box" +" --> Check the box 'Edit filter settings' --> Save`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:293 +msgid "" +"Microsoft Excel can modify the encoding when saving (:menuselection:`'Save " +"As' dialog box --> 'Tools' drop-down menu --> Encoding tab`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:297 +msgid "Difference between Database ID and External ID" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:299 +msgid "" +"Some fields define a relationship with another object. For example, the " +"country of a contact is a link to a record of the 'Country' object. When " +"such fields are imported, Odoo has to recreate links between the different " +"records. To help import such fields, Odoo provides three mechanisms." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:304 +msgid "**Only one** mechanism should be used per field that is imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:306 +msgid "" +"For example, to reference the country of a contact, Odoo proposes three " +"different fields to import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:308 +msgid ":guilabel:`Country`: the name or code of the country" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:309 +msgid "" +":guilabel:`Country/Database ID`: the unique Odoo ID for a record, defined by" +" the ID PostgreSQL column" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:311 +msgid "" +":guilabel:`Country/External ID`: the ID of this record referenced in another" +" application (or the `.XML` file that imported it)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:314 +msgid "" +"For the country of Belgium, for example, use one of these three ways to " +"import:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:316 +msgid ":guilabel:`Country`: `Belgium`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:317 +msgid ":guilabel:`Country/Database ID`: `21`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:318 +msgid ":guilabel:`Country/External ID`: `base.be`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:320 +msgid "" +"According to the company's need, use one of these three ways to reference " +"records in relations. Here is an example when one or the other should be " +"used, according to the need:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:323 +msgid "" +"Use :guilabel:`Country`: this is the easiest way when data comes from " +":abbr:`CSV (Comma-separated Values)` files that have been created manually." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:325 +msgid "" +"Use :guilabel:`Country/Database ID`: this should rarely be used. It is " +"mostly used by developers as the main advantage is to never have conflicts " +"(there may be several records with the same name, but they always have a " +"unique Database ID)" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:328 +msgid "" +"Use :guilabel:`Country/External ID`: use *External ID* when importing data " +"from a third-party application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:331 +msgid "" +"When *External IDs* are used, import :abbr:`CSV (Comma-separated Values)` " +"files with the :guilabel:`External ID` (ID) column defining the *External " +"ID* of each record that is imported. Then, a reference can be made to that " +"record with columns, like `Field/External ID`. The following two :abbr:`CSV " +"(Comma-separated Values)` files provide an example for products and their " +"categories." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:336 +msgid "" +":download:`CSV file for categories " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:338 +msgid "" +":download:`CSV file for Products " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:344 +msgid "Import relation fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:346 +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, the records of the related object need to be imported first, from" +" their own list menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:350 +msgid "" +"This can be achieved by using either the name of the related record, or its " +"ID, depending on the circumstances. The ID is expected when two records have" +" the same name. In such a case add `/ ID` at the end of the column title " +"(e.g. for product attributes: `Product Attributes / Attribute / ID`)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:355 +msgid "Options for multiple matches on fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:357 +msgid "" +"If, for example, there are two product categories with the child name " +"`Sellable` (e.g. `Misc. Products/Sellable` & `Other Products/Sellable`), the" +" validation is halted, but the data may still be imported. However, Odoo " +"recommends that the data is not imported because it will all be linked to " +"the first `Sellable` category found in the *Product Category* list (`Misc. " +"Products/Sellable`). Odoo, instead, recommends modifying one of the " +"duplicate's values, or the product category hierarchy." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:364 +msgid "" +"However, if the company does not wish to change the configuration of product" +" categories, Odoo recommends making use of the *External ID* for this field," +" 'Category'." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:368 +msgid "Import many2many relationship fields" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:370 +msgid "" +"The tags should be separated by a comma, without any spacing. For example, " +"if a customer needs to be linked to both tags: `Manufacturer` and `Retailer`" +" then 'Manufacturer,Retailer' needs to be encoded in the same column of the " +":abbr:`CSV (Comma-separated Values)` file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:374 +msgid "" +":download:`CSV file for Manufacturer, Retailer " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:377 +msgid "Import one2many relationships" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:379 +msgid "" +"If a company wants to import a sales order with several order lines, a " +"specific row **must** be reserved in the :abbr:`CSV (Comma-separated " +"Values)` file for each order line. The first order line is imported on the " +"same row as the information relative to order. Any additional lines need an " +"additional row that does not have any information in the fields relative to " +"the order." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:384 +msgid "" +"As an example, here is a :abbr:`CSV (Comma-separated Values)` file of some " +"quotations that can be imported, based on demo data:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:387 +msgid "" +":download:`File for some Quotations " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:390 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"purchase orders with their respective purchase order lines:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:393 +msgid "" +":download:`Purchase orders with their respective purchase order lines " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:396 +msgid "" +"The following :abbr:`CSV (Comma-separated Values)` file shows how to import " +"customers and their respective contacts:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:399 +msgid "" +":download:`Customers and their respective contacts " +"`" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:403 +msgid "Import image files" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:405 +msgid "" +"To import image files along with the :ref:`uploaded " +"` CSV or Excel file, follow the " +"next steps:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:408 +msgid "" +"Add the image file names to the relevant :guilabel:`Image` column in the " +"data file." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:409 +msgid "" +":ref:`Upload the data file ` or " +"reload it by clicking :guilabel:`Load Data File`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:411 +msgid "" +"Click :guilabel:`Upload your files` under the :guilabel:`Files to import` " +"section." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:412 +msgid "" +"Select the relevant image files. The number of files selected appears next " +"to the button." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:413 +msgid "Click :guilabel:`Test` to verify that all data is valid." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:414 +msgid "" +"Click :guilabel:`Import`. During the import process, Odoo performs a file " +"check to automatically link the uploaded images to the imported data file. " +"If there is no match, the data file is imported without any image." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:419 +msgid "" +"The :guilabel:`Files to import` section is enabled if your product template " +"has an :guilabel:`Image` column with all fields populated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:421 +msgid "" +"The image file names in the data file must correspond to the uploaded image " +"files." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:422 +msgid "" +"When importing a large number of images, you can specify the maximum batch " +"size in megabytes and set a delay to prevent the system from becoming " +"overloaded. To do so, :doc:`enable the developer mode " +"<../general/developer_mode>` and fill in the :guilabel:`Max size per batch` " +"and the :guilabel:`Delay after each batch` fields in the :guilabel:`Files to" +" import` section. By default, the delay meets the RPC/API call limit defined" +" in the `Odoo Cloud - Acceptable Use Policy " +"`_." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:430 +msgid "Import records several times" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:432 +msgid "" +"If an imported file contains one of the columns: :guilabel:`External ID` or " +":guilabel:`Database ID`, records that have already been imported are " +"modified, instead of being created. This is extremely useful as it allows " +"users to import the same :abbr:`CSV (Comma-separated Values)` file several " +"times, while having made some changes in between two imports." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:437 +msgid "" +"Odoo takes care of creating or modifying each record, depending if it is new" +" or not." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:439 +msgid "" +"This feature allows a company to use the *Import/Export tool* in Odoo to " +"modify a batch of records in a spreadsheet application." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:443 +msgid "Value not provided for a specific field" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:445 +msgid "" +"If all fields are not set in the CSV file, Odoo assigns the default value " +"for every non-defined field. But, if fields are set with empty values in the" +" :abbr:`CSV (Comma-separated Values)` file, Odoo sets the empty value in the" +" field, instead of assigning the default value." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:450 +msgid "Export/import different tables from an SQL application to Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:452 +msgid "" +"If data needs to be imported from different tables, relations need to be " +"recreated between records belonging to different tables. For instance, if " +"companies and people are imported, the link between each person and the " +"company they work for needs to be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:456 +msgid "" +"To manage relations between tables, use the `External ID` facilities of " +"Odoo. The `External ID` of a record is the unique identifier of this record " +"in another application. The `External ID` must be unique across all records " +"of all objects. It is a good practice to prefix this `External ID` with the " +"name of the application or table. (like, 'company_1', 'person_1' - instead " +"of '1')" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:461 +msgid "" +"As an example, suppose there is an SQL database with two tables that are to " +"be imported: companies and people. Each person belongs to one company, so " +"the link between a person and the company they work for must be recreated." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:465 +msgid "" +"Test this example, with a :download:`sample of a PostgreSQL database " +"`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:468 +msgid "" +"First, export all companies and their *External ID*. In PSQL, write the " +"following command:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:474 +msgid "" +"This SQL command creates the following :abbr:`CSV (Comma-separated Values)` " +"file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:483 +msgid "" +"To create the :abbr:`CSV (Comma-separated Values)` file for people linked to" +" companies, use the following SQL command in PSQL:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:490 +msgid "It produces the following :abbr:`CSV (Comma-separated Values)` file:" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:500 +msgid "" +"In this file, Fabien and Laurence are working for the Bigees company " +"(`company_1`), and Eric is working for the Organi company. The relation " +"between people and companies is done using the *External ID* of the " +"companies. The *External ID* is prefixed by the name of the table to avoid a" +" conflict of ID between people and companies (`person_1` and `company_1`, " +"who shared the same ID 1 in the original database)." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:506 +msgid "" +"The two files produced are ready to be imported in Odoo without any " +"modifications. After having imported these two :abbr:`CSV (Comma-separated " +"Values)` files, there are four contacts and three companies (the first two " +"contacts are linked to the first company). Keep in mind to first import the " +"companies, and then the people." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:514 +msgid "Update data in Odoo" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:516 +msgid "" +"Existing data can be updated in bulk through a data import, as long as the " +":ref:`External ID ` remains consistent." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:520 +msgid "Prepare data export" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:522 +msgid "" +"To update data through an import, first navigate to the data to be updated, " +"and select the |list| to activate list view. On the far-left side of the " +"list, tick the checkbox for any record to be updated. Then, click |actions|," +" and select :icon:`fa-upload` :guilabel:`Export` from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:527 +msgid "" +"On the resulting :guilabel:`Export Data` pop-up window, tick the checkbox " +"labeled, :guilabel:`I want to update data (import-compatible export)`. This " +"automatically includes the *External ID* in the export. Additionally, it " +"limits the :guilabel:`Fields to export` list to **only** include fields that" +" are able to be imported." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:533 +msgid "" +"The :guilabel:`External ID` field does **not** appear in the " +":guilabel:`Fields to export` list unless it is manually added, but it is " +"still included in the export. However, if the :guilabel:`I want to update " +"data (import-compatible export)` checkbox is ticked, it is included in the " +"export." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:537 +msgid "" +"Select the required fields to be included in the export using the " +":ref:`options ` on the pop-up " +"window, then click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:541 +msgid "Import updated data" +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:543 +msgid "" +"After exporting, make any necessary changes to the data file. When the file " +"is ready, it can be :ref:`imported ` by following the same process as a normal data import." +msgstr "" + +#: ../../content/applications/essentials/export_import_data.rst:548 +msgid "" +"When updating data, it is extremely important that the *External ID* remain " +"consistent, as this is how the system identifies a record. If an ID is " +"altered, or removed, the system may add a duplicate record, instead of " +"updating the existing one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:5 +msgid "Odoo rich-text editor" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:7 +msgid "" +"The Odoo rich-text editor allows creating and editing rich-text content in " +"HTML fields, such as the :guilabel:`Internal Notes` and " +":guilabel:`Description` fields, as well as in the :ref:`Knowledge articles " +"` and the :ref:`Studio report " +"editor `, among others. Start typing or " +"use the :ref:`toolbar ` or :ref:`powerbox " +"` for formatting and structuring text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:15 +msgid "" +"Hover over any element in the text (header, table, clipboard, etc.) to " +"reveal the :icon:`fa-sort` :guilabel:`(drag)` icon. Click and hold the icon " +"to drag and drop the element elsewhere in the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:22 +msgid "Text editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:24 +msgid "" +"To edit a word, sentence, or paragraph, select or double-click it to display" +" the text editor toolbar and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:27 +msgid "" +"**Font style**: Change the style using various options, such as " +":guilabel:`Header 1 to 6, Normal, Paragraph, Code`, and :guilabel:`Quote`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:29 +msgid ":guilabel:`B`: Put the text in bold." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:30 +msgid ":guilabel:`I`: Put the text in italics." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:31 +msgid ":guilabel:`U`: Underline the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:32 +msgid ":guilabel:`S`: Strike through the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:33 +msgid "" +":guilabel:`A` and :icon:`fa-paint-brush` :guilabel:`(paintbrush)` to " +"customize the font and background colors, respectively:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:36 +msgid "" +":guilabel:`Solid`: Select the preferred color from the predefined palette." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:37 +msgid "" +":guilabel:`Custom`: Customize the color palette using the wheel or by " +"configuring the :guilabel:`hex` code and :guilabel:`RGBA` values." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:39 +msgid "" +":guilabel:`Gradient`: Select a predefined gradient or customize it by " +"choosing between :guilabel:`Linear` or :guilabel:`Radial` and adjusting the " +"wheel." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:42 +msgid "**Font size**: Adjust the size of the text." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:43 +msgid "" +":icon:`fa-list-ul` (:guilabel:`bulleted list`): Turn the text into a " +"bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:44 +msgid "" +":icon:`fa-list-ol` (:guilabel:`numbered list`): Turn the text into a " +"numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:45 +msgid "" +":icon:`fa-check-square-o` (:guilabel:`checklist`): Turn the text into a " +"checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:46 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert or edit a URL link to a selected " +"text, and optionally upload an image using its file URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:48 +msgid "" +":guilabel:`Translate`: Translate the content in the :doc:`installed " +"languages `." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:50 +msgid "" +":icon:`fa-magic` :guilabel:`AI` (:guilabel:`ChatGPT`): Get AI-generated " +"suggestions and adjust the tone by clicking buttons such as " +":guilabel:`Correct, Shorten, Lengthen, Friendly, Professional`, and " +":guilabel:`Persuasive`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:-1 +msgid "Text editor's toolbox" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "Use the following keyboard shortcuts to apply formatting:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:60 +msgid "" +"**Emphasis**: Press `CTRL`/`CMD` + `B`, `CTRL`/`CMD` + `I`, or `CTRL`/`CMD` " +"+ `U` to apply the bold, italics, or underlined effect." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:62 +msgid "" +"**Numbered list**: Type `1.`, `1)`, `A.`, or `A)` to start a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:63 +msgid "**Bulleted list**: Type `*` or `-` to start a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:68 +msgid "Powerbox commands" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:70 +msgid "" +"To use a command, type `/` to open the powerbox, then enter the command's " +"name or select from multiple features to insert tables, images, banners, " +"etc." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:74 +msgid "" +"Starting a new paragraph displays a tooltip with command shortcut icons. " +"Click an icon to add the command, or click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon to open the powerbox for all commands." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:79 +msgid "" +"Commands specific to particular apps are excluded from this description." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:82 +msgid "Structure" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:89 +#: ../../content/applications/essentials/html_editor.rst:124 +#: ../../content/applications/essentials/html_editor.rst:142 +#: ../../content/applications/essentials/html_editor.rst:162 +#: ../../content/applications/essentials/html_editor.rst:180 +#: ../../content/applications/essentials/html_editor.rst:205 +#: ../../content/applications/essentials/html_editor.rst:221 +#: ../../content/applications/essentials/html_editor.rst:233 +msgid "Command" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:90 +#: ../../content/applications/essentials/html_editor.rst:125 +#: ../../content/applications/essentials/html_editor.rst:143 +#: ../../content/applications/essentials/html_editor.rst:163 +#: ../../content/applications/essentials/html_editor.rst:181 +#: ../../content/applications/essentials/html_editor.rst:206 +#: ../../content/applications/essentials/html_editor.rst:222 +#: ../../content/applications/essentials/html_editor.rst:234 +#: ../../content/applications/essentials/property_fields.rst:34 +msgid "Use" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:91 +#: ../../content/applications/essentials/property_fields.rst:83 +msgid ":guilabel:`Separator`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:92 +msgid "Insert a horizontal rule separator." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:93 +msgid ":guilabel:`2 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:94 +msgid "Convert into 2 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:95 +msgid ":guilabel:`3 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:96 +msgid "Convert into 3 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:97 +msgid ":guilabel:`4 columns`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:98 +msgid "Convert into 4 columns." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:99 +msgid ":guilabel:`Table`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:100 +msgid "Insert a table." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:101 +msgid ":guilabel:`Bulleted list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:102 +msgid "Create a bulleted list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:103 +msgid ":guilabel:`Numbered list`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:104 +msgid "Create a numbered list." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:105 +msgid ":guilabel:`Checklist`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:106 +msgid "Create a checklist." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:107 +msgid ":guilabel:`Quote`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:108 +msgid "Add a blockquote section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:109 +msgid ":guilabel:`Code`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:110 +msgid "Add a code section." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:113 +msgid "" +"To organize a table, hover over a column or row to reveal the table menu. " +"Click the :icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon to move, insert," +" or delete a column or row." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:117 +msgid "Banner" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:126 +msgid ":guilabel:`Banner Info`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:127 +msgid "Insert an info banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:128 +msgid ":guilabel:`Banner Success`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:129 +msgid "Insert a success banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:130 +msgid ":guilabel:`Banner Warning`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:131 +msgid "Insert a warning banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:132 +msgid ":guilabel:`Banner Danger`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:133 +msgid "Insert a danger banner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:135 +msgid "Format" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:144 +msgid ":guilabel:`Heading 1`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:145 +msgid "Big section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:146 +msgid ":guilabel:`Heading 2`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:147 +msgid "Medium section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:148 +msgid ":guilabel:`Heading 3`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:149 +msgid "Small section heading." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:150 +msgid ":guilabel:`Text`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:151 +msgid "Paragraph block: Insert a paragraph." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:152 +msgid ":guilabel:`Switch direction`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:153 +msgid "Switch the text's direction." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:155 +msgid "Media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:164 +msgid ":guilabel:`Media`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:165 +msgid "" +":ref:`Insert an image ` or icon: :doc:`Search the Unsplash " +"database ` or upload images, " +"documents, or icons." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:167 +msgid ":guilabel:`Clipboard`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:168 +msgid "Add a clipboard section to store content and reuse it in other apps." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:169 +msgid ":guilabel:`Upload a file`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:170 +msgid "" +"Add a download box: share images, recordings, or documents that internal " +"users can download." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:173 +msgid "Navigation" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:182 +msgid ":guilabel:`Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:183 +msgid "" +"Add a link: Type the label and enter a URL or upload a file, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:185 +msgid ":guilabel:`Button`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:186 +msgid "" +"Add a button: Type the label, enter a URL or upload a file, select the " +"button style, type, and size, then click :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:188 +msgid ":guilabel:`Article`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:189 +msgid "" +"Insert a shortcut to a :doc:`Knowledge article " +"`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:190 +msgid ":guilabel:`Appointment`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:191 +msgid "" +"Add a specific appointment: Select one or several appointment type(s) to " +"assign to relevant users, then click :guilabel:`Insert a link`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:193 +msgid ":guilabel:`Table Of Content`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:194 +msgid "" +"Highlight the structure (headings): Create a table of content based on the " +"headings." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:195 +msgid ":guilabel:`Video Link`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:196 +msgid "" +"Insert a video: Copy-paste the video URL (Youtube, Vimeo, Dailymotion, and " +"Youku only)." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:198 +msgid "Widget" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:207 +msgid ":guilabel:`Emoji`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:208 +msgid "Add an emoji: search for the desired emoji." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:209 +msgid ":guilabel:`3 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:210 +msgid "Insert a rating of up to 3 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:211 +msgid ":guilabel:`5 Stars`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:212 +msgid "Insert a rating of up to 5 stars." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:214 +msgid "AI Tools" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:223 +msgid ":guilabel:`ChatGPT`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:224 +msgid "Generate content with AI." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:226 +msgid "Basic Block" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:235 +msgid ":guilabel:`Signature`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:236 +msgid "Insert your signature." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:241 +msgid "Insert media" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:243 +msgid "" +"To insert media, type `/Media` or click the :icon:`fa-file-image-o` " +":guilabel:`(image)` icon in the tooltip, then choose from the following " +"tabs:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:246 +msgid ":guilabel:`Images`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:248 +msgid "" +"Search the :doc:`Unsplash ` " +"database to find a suitable image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:250 +msgid ":guilabel:`Add URL`: Copy-paste the **image address**." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:251 +msgid ":guilabel:`Upload an image`: Upload an image into the library." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:253 +msgid ":guilabel:`Documents`" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:255 +msgid "Search for a document in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:256 +msgid ":guilabel:`Add URL`: Copy-paste a valid URL." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:257 +msgid ":guilabel:`Upload a document`: Upload a document from a local drive." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:259 +msgid ":guilabel:`Icons`: Search an icon from the selection in the database." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:262 +msgid "Media editor toolbar" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:264 +msgid "" +"After :ref:`inserting an image `, click it to display the " +"media editor toolbar, and apply any of the following formatting options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:267 +msgid "" +":icon:`fa-search-plus` (:guilabel:`preview`): Preview the image, zoom in or " +"out, print it or download it. Exit the preview by clicking the :icon:`fa-" +"times` :guilabel:`(close)` icon in the top right corner." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:270 +msgid "" +":guilabel:`Description`: Edit the image description and tooltip, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:271 +msgid "" +":icon:`fa-square` (:guilabel:`rounded`): Apply a rounded shape to the " +"corners of the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:272 +msgid "" +":icon:`fa-circle-o` (:guilabel:`circle`): Apply a circular shape to the " +"image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:273 +msgid "" +":icon:`fa-sun-o` (:guilabel:`shadow`): Apply a shadow effect to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:274 +msgid ":icon:`fa-picture-o` (:guilabel:`image`): Apply a border to the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:275 +msgid "" +":icon:`fa-plus-square-o` (:guilabel:`padding`): Add an image padding and " +"choose from small, medium, large, or extra large sizes." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:277 +msgid ":guilabel:`Default`: Restore the image to its default size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:278 +msgid ":guilabel:`100%`: Set the image to full size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:279 +msgid ":guilabel:`50%`: Set the image to half its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:280 +msgid ":guilabel:`25%`: Set the image to a quarter of its size." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:281 +msgid "" +":icon:`fa-object-ungroup` (:guilabel:`object`): Resize and rotate the image." +" Click the :icon:`fa-object-ungroup` :guilabel:`(object)` icon a second time" +" to reset the transformation." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:283 +msgid "" +":icon:`fa-crop` (:guilabel:`crop`): Crop the image manually or apply the " +"following options:" +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:285 +msgid "" +"Choose from the `Flexible`, `16:9`, `4:3`, `1:1`, or `2:3` aspect ratios." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:286 +msgid "Zoom in or out." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:287 +msgid "Rotate left or right." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:288 +msgid "Flip horizontally or vertically." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:289 +msgid "Reset the image." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:291 +msgid "" +":guilabel:`Replace`: Replace the image by searching in the :doc:`Unsplash " +"` database, adding a URL, or " +"uploading a different one." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:294 +msgid "" +":icon:`fa-link` (:guilabel:`link`): Insert a link to the image, type the " +"URL, then click :guilabel:`Apply`. To remove the link, click the :icon:`fa-" +"chain-broken` :guilabel:`(unlink)` icon." +msgstr "" + +#: ../../content/applications/essentials/html_editor.rst:296 +msgid ":icon:`fa-trash` (:guilabel:`trash`): Remove the image." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:3 +msgid "In-app purchases (IAP)" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:7 +msgid "" +"In-app purchases (IAP) are optional services that enhance Odoo databases. " +"Each service provides its own specific features and functionality. A full " +"list of services is available on the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "The IAP catalog with various services available on IAP.Odoo.com." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:15 +msgid "" +"The :guilabel:`SMS` service sends text messages to contacts directly from " +"the database, and the :guilabel:`Documents Digitization` service digitizes " +"scanned or PDF vendor bills, expenses, and resumes with optical character " +"recognition (OCR) and artificial intelligence (AI)." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:19 +msgid "" +"|IAP| services do **not** need to be configured or set up before use. Odoo " +"users can click on the service in the app to activate it. However, each " +"service requires its own prepaid credits, and when they run out, users " +"**must** :ref:`buy more ` in order to keep using it." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:24 +msgid "" +"Enterprise Odoo users with a valid subscription get free credits to test IAP" +" features before deciding to purchase more credits for the database. This " +"includes demo/training databases, educational databases, and one-app-free " +"databases." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:31 +msgid "IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:33 +msgid "" +"|IAP| services are provided by Odoo, as well as third-parties, and have a " +"wide range of uses." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:35 +msgid "The following |IAP| services are offered by Odoo:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:37 +msgid "" +":guilabel:`Documents Digitization`: digitizes scanned or PDF vendor bills, " +"expenses, and resumes with OCR and AI." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:39 +msgid "" +":guilabel:`Partner Autocomplete`: automatically populates contact records " +"with corporate data." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:40 +msgid "" +":guilabel:`SMS`: sends SMS text messages to contacts directly from the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:41 +msgid "" +":guilabel:`Lead Generation`: generates leads based on a set of criteria, and" +" converts web visitors into quality leads and opportunities." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:43 +msgid "" +":guilabel:`Snailmail`: sends customer invoices and follow-up reports by " +"post, worldwide." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:44 +msgid "" +":guilabel:`Signer identification with itsme®`: Ask document signatories in " +"Odoo **Sign** to provide their identity using the *itsme* :icon:`fa-" +"registered` identity platform, which is available in Belgium and the " +"Netherlands." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:48 +msgid "" +"For more information on every service currently available (offered from " +"developers other than Odoo), visit the `Odoo IAP Catalog " +"`_." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:52 +msgid "Use IAP services" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:54 +msgid "" +"|IAP| services are automatically integrated with Odoo, and do **not** " +"require users to configure any settings. To use a service, interact with it " +"wherever it appears in the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:58 +msgid "" +"The following flow focuses on the *SMS* |IAP| service being used from a " +"contact's record." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:60 +msgid "" +"This can be done by clicking the :icon:`fa-mobile` :guilabel:`SMS` icon " +"within the database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS icon on a typical contact information form located within an Odoo " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:65 +msgid "" +"One way to utilize the *SMS* |IAP| service with Odoo is showcased in the " +"following steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:67 +msgid "" +"First, navigate to the :menuselection:`Contacts application`, and click on a" +" contact with a mobile phone number entered in either the :guilabel:`Phone` " +"or :guilabel:`Mobile` field of the contact form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:71 +msgid "" +"Next, find the :icon:`fa-mobile` :guilabel:`SMS` icon that appears to the " +"right of the :guilabel:`Phone` or :guilabel:`Mobile` fields. Click the " +":icon:`fa-mobile` :guilabel:`SMS` icon, and a :guilabel:`Send SMS Text " +"Message` pop-up window appears." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:75 +msgid "" +"Type a message in the :guilabel:`Message` field of the pop-up window. Then, " +"click the :guilabel:`Send SMS` button. Odoo then sends the message, via SMS," +" to the contact, and logs what was sent in the *chatter* of the contact's " +"form." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:79 +msgid "" +"Upon sending the SMS message, the prepaid credits for the *SMS* |IAP| " +"service are automatically deducted from the existing credits. If there are " +"not enough credits to send the message, Odoo prompts the user to purchase " +"more." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:84 +msgid "" +"For more information on how to use various |IAP| services, and for more in-" +"depth instructions related to SMS functionality in Odoo, review the " +"documentation below:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:87 +msgid ":doc:`Lead mining <../sales/crm/acquire_leads/lead_mining>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:88 +msgid "" +":doc:`Enrich your contacts base with Partner Autocomplete " +"<../sales/crm/optimize/partner_autocomplete>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:90 +msgid ":doc:`SMS Marketing <../marketing/sms_marketing>`" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:95 +msgid "IAP credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:97 +msgid "" +"Every time an |IAP| service is used, the prepaid credits for that service " +"are spent. Odoo prompts the purchase of more credits when there are not " +"enough credits left to continue using a service. Email alerts can also be " +"set up for when :ref:`credits are low `." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:101 +msgid "" +"Credits are purchased in *Packs* from the `Odoo IAP Catalog " +"`_, and pricing is specific to" +" each service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:105 +msgid "" +"The `SMS service `_ has four " +"packs available, in denominations of:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:108 +msgid ":guilabel:`Starter Pack`: 10 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:109 +msgid ":guilabel:`Standard Pack`: 100 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:110 +msgid ":guilabel:`Advanced Pack`: 500 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:111 +msgid ":guilabel:`Expert Pack`: 1,000 credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "Four different packs of credits for the SMS IAP service." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:116 +msgid "" +"The number of credits consumed depends on the length of the SMS and the " +"country of destination." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:118 +msgid "" +"For more information, refer to the :doc:`SMS Pricing and FAQ " +"<../marketing/sms_marketing/pricing_and_faq>` documentation." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:124 +msgid "Buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:126 +msgid "" +"If there are not enough credits to perform a task, the database " +"automatically prompts the purchase of more credits." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:129 +msgid "" +"Users can check the current balance of credits for each service, and " +"manually purchase more credits, by navigating to the " +":menuselection:`Settings app --> Contacts section`, and beneath the " +":guilabel:`Odoo IAP` setting, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:133 +msgid "" +"Doing so reveals an :guilabel:`IAP Service` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:138 +msgid "Manually buy credits" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:140 +msgid "To manually buy credits in Odoo, follow these steps:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:142 +msgid "" +"First, go to the :menuselection:`Settings application` and type `IAP` in the" +" search bar. Alternatively users can scroll down to the :guilabel:`Contacts`" +" section. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The Settings app showing the Odoo IAP heading and View My Services button." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:150 +msgid "" +"Doing so reveals an :guilabel:`IAP Account` page, listing the various |IAP| " +"services in the database. From here, click an |IAP| service to open its " +":guilabel:`Account Information` page, where additional credits can be " +"purchased." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:154 +msgid "" +"On the :guilabel:`Account Information` page, click the :guilabel:`Buy " +"Credit` button. Doing so loads a :guilabel:`Buy Credits for (IAP Account)` " +"page in a new tab. From here, click :guilabel:`Buy` on the desired pack of " +"credits. Then, follow the prompts to enter payment details, and confirm the " +"order." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:-1 +msgid "" +"The SMS service page on IAP.Odoo.com with four packs of credits available " +"for purchase." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:162 +msgid "" +"Once the transaction is complete, the credits are available for use in the " +"database." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:167 +msgid "Low-credit notification" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:169 +msgid "" +"It is possible to be notified when credits are low, in order to avoid " +"running out of credits, while using an |IAP| service. To do that, follow " +"this process:" +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:172 +msgid "" +"Go to the :menuselection:`Settings application`, and type `IAP` in the " +"search bar. Under the :guilabel:`Contacts` section, where it says " +":guilabel:`Odoo IAP`, click :guilabel:`View My Services`." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:176 +msgid "" +"The available |IAP| accounts appear in a list view on the :guilabel:`IAP " +"Account` page. From here, click on the desired |IAP| account to view that " +"service's :guilabel:`Account Information` page." +msgstr "" + +#: ../../content/applications/essentials/in_app_purchase.rst:179 +msgid "" +"Set the :guilabel:`Email Alert Threshold` to the credit amount that should " +"trigger a low-credit alert when the balance falls below it. Next, select " +"which user(s) should receive the email notification using the " +":guilabel:`Email Alert Recipients` field." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:3 +msgid "Keyboard shortcuts" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:5 +msgid "" +"Users in Odoo can utilize several keyboard shortcuts to navigate through " +"modules, execute actions, and manage data." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:9 +msgid "" +"Hold :kbd:`Ctrl` to view the keyboard shortcuts assigned to each element on " +"the interface." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "A selection of keyboard shortcuts in Odoo." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:16 +msgid "" +"Some keyboard shortcuts may not be available on different versions of Odoo " +"or effective depending on browsers, extensions, or other individual " +"settings." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:20 +msgid "Keyboard shortcuts by operating system" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:22 +msgid "" +"Below is a list of some of the most commonly used keyboard shortcuts within " +"Odoo, listed by operating system." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:29 +msgid "Description" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:30 +msgid "Windows / Linux" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:31 +msgid "macOS" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:32 +msgid "Previous breadcrumb" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:33 +msgid ":kbd:`Alt` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:34 +msgid ":kbd:`Ctrl` + :kbd:`B`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:35 +msgid "Create new record" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:36 +msgid ":kbd:`Alt` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:37 +msgid ":kbd:`Ctrl` + :kbd:`C`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:38 +msgid "Odoo Home Page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:39 +msgid ":kbd:`Alt` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:40 +msgid ":kbd:`Ctrl` + :kbd:`H`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:41 +msgid "Discard changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:42 +msgid ":kbd:`Alt` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:43 +msgid ":kbd:`Ctrl` + :kbd:`J`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:44 +msgid "Save changes" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:45 +msgid ":kbd:`Alt` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:46 +msgid ":kbd:`Ctrl` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:47 +msgid "Next page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:48 +msgid ":kbd:`Alt` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:49 +msgid ":kbd:`Ctrl` + :kbd:`N`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:50 +msgid "Previous page" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:51 +msgid ":kbd:`Alt` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:52 +msgid ":kbd:`Ctrl` + :kbd:`P`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:53 +msgid "Search" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:54 +msgid ":kbd:`Alt` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:55 +msgid ":kbd:`Ctrl` + :kbd:`Q`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:56 +msgid "Select menus" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:57 +msgid ":kbd:`Alt` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:58 +msgid ":kbd:`Ctrl` + :kbd:`1-9`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:59 +msgid "Create a new To-Do" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:60 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:61 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`T`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:62 +msgid "Search a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:63 +msgid ":kbd:`Alt` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:64 +msgid ":kbd:`Ctrl` + :kbd:`F`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:65 +msgid "Share a Knowledge article" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:66 +msgid ":kbd:`Alt` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:67 +msgid ":kbd:`Ctrl` + :kbd:`Shift` + :kbd:`S`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:68 +msgid "Open command palette" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:69 +msgid ":kbd:`Ctrl` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:70 +msgid ":kbd:`Command` + :kbd:`K`" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:73 +msgid "" +"After opening the command palette, search using the following keyboard " +"shortcuts:" +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:75 +msgid ":kbd:`/`: search for menus, applications, and modules." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:76 +msgid ":kbd:`@`: search for users." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:77 +msgid ":kbd:`#`: search for **Discuss** channels." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:78 +msgid ":kbd:`?`: search for **Knowledge** articles." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:80 +msgid "" +"Enter a name (or term) in the search bar, or use the arrow keys to scroll " +"through the available options. Then, click :kbd:`Ctrl` + :kbd:`Enter` to " +"open the selected app, module, or menu in a new tab." +msgstr "" + +#: ../../content/applications/essentials/keyboard_shortcuts.rst:0 +msgid "The command palette in Odoo, with the menu search option selected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:3 +msgid "Property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:5 +msgid "" +"Property fields, or properties, enable the customization of a :ref:`form " +"` view by adding various :ref:`field types " +"`. These fields allow information storage and management" +" by adding values." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:9 +msgid "Property vs. regular fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:11 +msgid "" +"Properties act as pseudo-fields; they behave like regular fields but are not" +" saved as columns in the database. They also rely on a defined :ref:`parent " +"record `." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:15 +msgid "" +"Adding a property to a *task* inserts a field in *all tasks* within the " +"*same project* while other projects' tasks remain unaffected." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:21 +msgid "Add property fields" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:23 +msgid "" +"To add a first property field to a :ref:`form view " +"`, click the :icon:`fa-cog` (:guilabel:`Actions`)" +" icon, then select :icon:`fa-cogs` :guilabel:`Add Properties`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:26 +msgid "" +"In the popover, enter the property's :guilabel:`Label`, choose a " +":guilabel:`Field Type`, and then configure the field based on the selected " +"type:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:33 +msgid "Field type" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:35 +msgid "Options" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:36 +msgid ":ref:`Text `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:37 +msgid "Short text on a single line" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:38 +#: ../../content/applications/essentials/property_fields.rst:44 +#: ../../content/applications/essentials/property_fields.rst:47 +msgid "Enter a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:39 +msgid ":ref:`Checkbox `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:40 +msgid "Checked or unchecked status" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:41 +msgid "Choose the :guilabel:`Default State`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:42 +msgid ":ref:`Integer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:43 +msgid "" +"Integer numbers (:dfn:`positive, negative, or zero, without a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:45 +msgid ":ref:`Decimal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:46 +msgid "Decimal numbers (:dfn:`positive, negative, or zero, with a decimal`)" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:48 +msgid ":ref:`Date `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:49 +msgid "Selection of a date on a calendar" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:50 +#: ../../content/applications/essentials/property_fields.rst:53 +#: ../../content/applications/essentials/property_fields.rst:76 +#: ../../content/applications/essentials/property_fields.rst:82 +msgid "Select a :guilabel:`Default Value` if desired." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:51 +msgid ":ref:`Date & Time `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:52 +msgid "Selection of a date on a calendar and a time on a clock" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:54 +msgid ":ref:`Selection `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:55 +msgid "Selection of a value from a group of predefined values" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:56 +msgid "" +"Add a selectable option by clicking :icon:`fa-plus` :guilabel:`Add a Value` " +"and entering the :guilabel:`Option Name`." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:59 +msgid "" +"If desired, set an option as default by clicking the :icon:`fa-star-o` " +"(:guilabel:`Select Default`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:62 +msgid "" +"Reorder the options by dragging and dropping them using the :icon:`oi-" +"draggable` (:guilabel:`drag handle`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:65 +msgid "" +"Delete an option by clicking the :icon:`fa-trash-o` (:guilabel:`Remove " +"Property`) button." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:66 +msgid ":ref:`Tags `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:67 +msgid "Selection of multiple values in the form of tags" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:68 +msgid "Enter a :guilabel:`Tag` name and press `Enter` to save it." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:70 +msgid "Change a tag's color by clicking it and selecting another one." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:71 +msgid ":ref:`Many2one `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:72 +msgid "Selection of a single record from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:73 +#: ../../content/applications/essentials/property_fields.rst:79 +msgid "" +"Enter the :guilabel:`Model` name. Configure its :ref:`Domain ` to filter records if needed." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:77 +msgid ":ref:`Many2many `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:78 +msgid "Selection of multiple records from another model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:84 +msgid "Group several properties under a foldable label" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:87 +msgid "Click outside the popover to save the added property." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:90 +msgid "" +"Select whether to display the property in the Kanban, List, or Calendar " +"views cards for every field with the :guilabel:`Display in Cards` option." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:92 +msgid "" +"To add another property, click :icon:`fa-plus` :guilabel:`Add a Property` at" +" the bottom of the form while in :icon:`fa-cogs` :guilabel:`Add Properties` " +"mode." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:96 +msgid "To edit an existing property, hover the cursor over the property:" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:98 +msgid "" +"Click the :icon:`fa-pencil` (:guilabel:`pencil`) button to open a popover " +"and modify the property. In the popover, click the :icon:`fa-chevron-up` " +"(up) or :icon:`fa-chevron-down` (down) chevron to move a property upwards or" +" downwards." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:101 +msgid "" +"Click :icon:`fa-trash` :guilabel:`Delete`, then :guilabel:`Delete` to delete" +" it. Deleting a property is permanent." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:103 +msgid "" +"Use the :icon:`oi-draggable` (:guilabel:`drag handle`) icon to drag and drop" +" the property to reorder or regroup." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:109 +msgid "Properties across apps" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:111 +msgid "" +"Property fields can be defined in the :ref:`form view " +"` of multiple models. Once set, the property is " +"shared by all records that are linked to the same *parent*." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:119 +msgid "App" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:120 +msgid "Model" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:121 +msgid "Parent" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:122 +msgid ":guilabel:`Accounting`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:123 +msgid ":ref:`Asset/Revenue Recognition `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:125 +msgid ":doc:`Loan `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:126 +msgid ":ref:`Asset model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:128 +msgid ":ref:`Journal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:129 +msgid ":guilabel:`Appraisals`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:130 +msgid ":ref:`Employee Appraisal `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:131 +msgid ":ref:`Department `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:132 +msgid ":guilabel:`CRM`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:133 +msgid "" +":doc:`Lead/Opportunity `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:134 +msgid ":ref:`Sales team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:135 +msgid ":guilabel:`Employees`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:136 +msgid ":ref:`Employee `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:137 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:138 +msgid ":guilabel:`Events`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:139 +msgid "" +":doc:`Event Registration `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:140 +msgid ":ref:`Event `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:141 +msgid ":guilabel:`Fleet`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:142 +msgid ":doc:`Vehicle `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:143 +msgid ":ref:`Vehicle model `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:144 +msgid ":guilabel:`Frontdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:145 +msgid ":ref:`Frontdesk Visitors `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:146 +msgid ":ref:`Station `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:147 +msgid ":guilabel:`Helpdesk`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:148 +msgid ":ref:`Ticket `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:149 +msgid ":ref:`Helpdesk team `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:150 +msgid ":guilabel:`Inventory`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:151 +msgid ":ref:`Lot/Serial `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:153 +msgid "" +":doc:`Transfer " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:156 +msgid ":ref:`Batch Transfer `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:157 +msgid ":ref:`Product variant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:159 +#: ../../content/applications/essentials/property_fields.rst:161 +msgid "" +":ref:`Operation type `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:162 +msgid ":guilabel:`Knowledge`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:163 +msgid ":ref:`Knowledge Article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:164 +msgid ":ref:`Parent article `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:165 +msgid ":guilabel:`Maintenance`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:166 +msgid "" +":ref:`Maintenance Equipment " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:167 +msgid "" +":ref:`Equipment category " +"`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:168 +msgid ":guilabel:`Meeting Rooms`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:169 +msgid "Room" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:170 +msgid "Office" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:171 +msgid ":guilabel:`Planning`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:172 +msgid ":ref:`Shift `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:173 +msgid ":ref:`Role `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:174 +msgid ":guilabel:`Project` / :guilabel:`Field Service`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:175 +msgid ":ref:`Task `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:176 +msgid ":ref:`Project `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:177 +msgid ":guilabel:`Recruitment`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:178 +msgid ":ref:`Applicant `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:180 +msgid ":ref:`Job Position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:182 +msgid "Candidate" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:183 +msgid ":ref:`Job position `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:185 +#: ../../content/applications/essentials/property_fields.rst:187 +#: ../../content/applications/essentials/property_fields.rst:190 +msgid ":ref:`Company `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:188 +msgid ":guilabel:`Repairs`" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:189 +msgid ":ref:`Repair order `" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:191 +msgid ":guilabel:`Sales` / etc." +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:192 +msgid "Product" +msgstr "" + +#: ../../content/applications/essentials/property_fields.rst:193 +msgid "Category" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:3 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:5 +msgid "" +"You can find several reports under the :guilabel:`Reporting` menu of most " +"apps that let you analyze and visualize the data of your records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:11 +msgid "Selecting a view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:13 +msgid "" +"Depending on the report, Odoo can display the data in various ways. " +"Sometimes, a unique view fully tailored to the report is available, while " +"several views are available for others. However, two generic views are " +"dedicated to reporting: the graph and pivot views." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:20 +msgid "Graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:22 +msgid "" +"The :ref:`graph view ` is used to visualize your " +"records' data, helping you identify patterns and trends. The view is often " +"found under the :guilabel:`Reporting` menu of apps but can be found " +"elsewhere. Click the **graph view button** located at the top right to " +"access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:33 +msgid "Pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:35 +msgid "" +"The :ref:`pivot view ` is used to aggregate your " +"records' data and break it down for analysis. The view is often found under " +"the :guilabel:`Reporting` menu of apps but can be found elsewhere. Click the" +" **pivot view button** located at the top right to access it." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:-1 +msgid "Selecting the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:45 +msgid "Choosing measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:47 +msgid "" +"After selecting a view, you should ensure only the relevant records are " +":doc:`filtered `. Next, you should choose what is measured. By " +"default, a measure is always selected. If you wish to edit it, click " +":guilabel:`Measures` and choose one or, only for pivots, multiple measures." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:52 +msgid "" +"When you select a measure, Odoo aggregates the values recorded on that field" +" for the filtered records. Only numerical fields (:ref:`integer " +"`, :ref:`decimal `, :ref:`monetary `) " +"can be measured. In addition, the :guilabel:`Count` option is used to count " +"the total number of filtered records." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:58 +msgid "" +"After choosing what you want to measure, you can define how the data should " +"be :ref:`grouped ` depending on the dimension you want to " +"analyze. By default, the data is often grouped by *Date > Month*, which is " +"used to analyze the evolution of a measure over the months." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:63 +msgid "" +"When you filter a single time period, the option to compare it against " +"another one appears." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Using the comparison option" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:72 +msgid "Select measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:74 +msgid "" +"Among other measures, you could add the :guilabel:`Margin` and " +":guilabel:`Count` measures to the Sales Analysis report. By default, the " +":guilabel:`Untaxed Amount` measure is selected." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Selecting different measures on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:81 +msgid "Group measures" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:83 +msgid "" +"You could group the measures by :guilabel:`Product Category` at the level of" +" rows on the previous Sales Analysis report example." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding a group on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:92 +msgid "Using the pivot view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:94 +msgid "" +"Grouping data is quintessential to the pivot view. It enables drilling down " +"the data to gain deeper insights. While you can use the :guilabel:`Group By`" +" option to quickly add a group at the level of rows, as shown in the example" +" above, you can also click the plus button (:guilabel:`➕`) next to the " +":guilabel:`Total` header at the level of rows *and* columns, and then select" +" one of the **preconfigured groups**. To remove one, click the minus button " +"(:guilabel:`➖`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:100 +msgid "" +"Once you have added a group, you can add new ones on the opposite axis or " +"the newly created subgroups." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:104 +msgid "" +"You could further divide the measures on the previous Sales Analysis report " +"example by the :guilabel:`Salesperson` group at the level of columns and by " +"the :guilabel:`Order Date > Month` group on the :guilabel:`All / Saleable / " +"Office Furniture` product category." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Adding multiple groups on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:112 +msgid "" +"Switch the rows and columns' groups by clicking the flip axis button " +"(:guilabel:`⇄`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:113 +msgid "" +"Click on a measure's label to sort the values by ascending (⏶) or descending" +" (⏷) order." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:114 +msgid "" +"Download a `.xlsx` version of the pivot by clicking the download button " +"(:guilabel:`⭳`)." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:119 +msgid "Using the graph view" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:121 +msgid "Three graphs are available: the bar, line, and pie charts." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:123 +msgid "" +"**Bar charts** are used to show the distribution or a comparison of several " +"categories. They are especially useful as they can deal with larger data " +"sets." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:126 +msgid "" +"**Line charts** are useful to show changing time series and trends over " +"time." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:128 +msgid "" +"**Pie charts** are used to show the distribution or a comparison of a small " +"number of categories when they form a meaningful whole." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:133 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:138 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:143 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Viewing the Sales Analysis report as a pie chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:149 +msgid "" +"For **bar** and **line** charts, you can use the stacked option when you " +"have at least two groups, which then appear on top of each other instead of " +"next to each other." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:154 +msgid "Stacked bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:159 +msgid "Regular bar chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked bar chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:164 +msgid "Stacked line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:169 +#: ../../content/applications/essentials/reporting.rst:184 +msgid "Regular line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Non-stacked line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:174 +msgid "" +"For **line** charts, you can use the cumulative option to sum values, which " +"is especially useful to show the change in growth over a time period." +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:179 +msgid "Cumulative line chart" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Cumulative line chart example" +msgstr "" + +#: ../../content/applications/essentials/reporting.rst:0 +msgid "Regular line chart example" +msgstr "" + +#: ../../content/applications/essentials/search.rst:3 +msgid "Search, filter, and group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:5 +msgid "" +"Odoo allows for the searching, filtering, and grouping of records in a view " +"to display only the most relevant records. The search bar is located at the " +"top of the view: start typing to :ref:`search for values `, " +"or click the :icon:`fa-caret-down` :guilabel:`(dropdown)` icon to access the" +" :ref:`Filter `, :ref:`Group By `, and " +":ref:`Favorites ` drop-down menus." +msgstr "" + +#: ../../content/applications/essentials/search.rst:14 +msgid "Search for values" +msgstr "" + +#: ../../content/applications/essentials/search.rst:16 +msgid "" +"Use the search field to look for specific values, and add them as a filter. " +"Type the value to search for (like a salesperson's name or a product), and " +"select the desired option from the drop-down menu to apply the search " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:21 +msgid "" +"Instead of adding a :ref:`custom filter ` to select " +"records where *Mitchell Admin* is the salesperson on the *Sales Analysis* " +"report (:menuselection:`Sales app --> Reporting --> Sales`), search for " +"`Mitch`, and click the :icon:`fa-caret-right` :guilabel:`(submenu)` icon " +"next to :guilabel:`Search Salesperson for: Mitch`, and select " +":guilabel:`Mitchell Admin`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Searching for a specific value on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:31 +msgid "" +"Using the search field is equivalent to using the *contains* operator when " +"adding a :ref:`custom filter `. If a partial value is" +" entered, and the desired field is directly selected (without selecting the " +":icon:`fa-caret-right` :guilabel:`(submenu)`, *all* records containing the " +"typed characters for the selected field are included." +msgstr "" + +#: ../../content/applications/essentials/search.rst:39 +msgid "Filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:41 +msgid "" +"Filters are used to select records that meet specific criteria. The default " +"selection of records is specific to each view, but can be modified by " +"selecting one (or several) :ref:`preconfigured filters " +"`, or by adding a :ref:`custom filter " +"`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:48 +msgid "Preconfigured filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:50 +msgid "" +"Modify the default selection of records by clicking the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` from the search bar, and selecting one (or " +"several) *preconfigured filters* from the :guilabel:`Filters` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:55 +msgid "" +"On the *Sales Analysis* report (:menuselection:`Sales app --> Reporting --> " +"Sales`), only records that are at the *sales order* stage, with an *order " +"date* within the last 365 days, are selected by default." +msgstr "" + +#: ../../content/applications/essentials/search.rst:59 +msgid "" +"To also include records at the *quotation* stage, select " +":guilabel:`Quotations` from the :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:62 +msgid "" +"Furthermore, to *only* include sales order and quotation records from a " +"specific year, like 2024, for example, first remove the existing `Order " +"Date: Last 365 Days` filter by clicking :icon:`fa-times` " +":guilabel:`(cancel)`, then select the :menuselection:`Order Date --> 2024` " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Using preconfigured filters on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:71 +msgid "" +"The preconfigured :guilabel:`Filters` are grouped, and each group is " +"separated by a horizontal line. Selecting preconfigured filters from the " +"same group allows records to match *any* of the applied conditions. However," +" selecting filters from different groups requires records to match *all* of " +"the applied conditions." +msgstr "" + +#: ../../content/applications/essentials/search.rst:79 +msgid "Custom filters" +msgstr "" + +#: ../../content/applications/essentials/search.rst:81 +msgid "" +"If the :ref:`preconfigured filters ` are not " +"specific enough, add a custom filter. To do so, click the :icon:`fa-caret-" +"down` :guilabel:`(dropdown)` icon in the search bar, then select " +":menuselection:`Filters --> Add Custom Filter`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:85 +msgid "" +"The :guilabel:`Add Custom Filter` pop-up window displays the matching " +"option, filter rule, and a toggle to :guilabel:`Include archived` records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The Add Custom Filter pop-up window." +msgstr "" + +#: ../../content/applications/essentials/search.rst:91 +msgid "" +"The default matching configuration is to :guilabel:`Match any of the " +"following rules`, indicating that each filter rule is applied independently." +" To change the matching configuration to :guilabel:`Match all of the " +"following rules`, at least two filter rules must be added to the custom " +"filter." +msgstr "" + +#: ../../content/applications/essentials/search.rst:96 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **All** of the filter rules must be met. Think of this as an *AND* " +"(`&`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:98 +msgid "" +":guilabel:`Match any` :icon:`fa-caret-down` :guilabel:`of the following " +"rules`: **Any** of the filter rules can be met. Think of this as an *OR* " +"(`|`) operation." +msgstr "" + +#: ../../content/applications/essentials/search.rst:101 +msgid "" +"By default, a single filter rule is added to the custom filter. The " +"following describes the structure of a filter rule:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:104 +msgid "" +"The first inline field is the *field name* to filter by. Some fields have " +"refined parameters that are nested within another field. These fields have a" +" :icon:`fa-caret-right` :guilabel:`(submenu)` icon beside them, which can be" +" selected to reveal the nested fields." +msgstr "" + +#: ../../content/applications/essentials/search.rst:107 +msgid "" +"The second inline field is the conditional *operator* used to compare the " +"field name to the value. The :ref:`available conditional operators " +"` are specific to the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:110 +msgid "" +"The third inline field is the variable *value* of the field name. The value " +"input may appear as a drop-down menu, a text input, a number input, a " +"date/time input, a boolean selector, or it may be blank, depending on the " +"operator used and the field's data type." +msgstr "" + +#: ../../content/applications/essentials/search.rst:114 +msgid "" +"Three inline buttons are also available to the right of the rule's filter " +"criteria:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:116 +msgid "" +":icon:`fa-plus` :guilabel:`(plus)`: Adds a new rule below the existing rule." +msgstr "" + +#: ../../content/applications/essentials/search.rst:117 +msgid "" +":icon:`fa-sitemap` :guilabel:`(node)`: Adds a new group of rules below the " +"existing rule, with the :guilabel:`any` and :guilabel:`all` matching options" +" available to define how each rule within this branch is applied to the " +"filter. If the matching option is set to the same as the parent group, the " +"fields are moved to join the parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:123 +msgid "" +"If the matching option is set to :guilabel:`Match all` :icon:`fa-caret-down`" +" :guilabel:`of the following rules`, and a new branch is added with its " +"matching option changed from :guilabel:`any` :icon:`fa-caret-down` " +":guilabel:`of` to :guilabel:`all` :icon:`fa-caret-down` :guilabel:`of`, the " +"newly-added branch disappears, and its group of rules are moved to the " +"parent group." +msgstr "" + +#: ../../content/applications/essentials/search.rst:129 +msgid "" +":icon:`fa-trash` :guilabel:`(delete)`: Deletes the node. If a branch node is" +" deleted, all children of that node are deleted, as well." +msgstr "" + +#: ../../content/applications/essentials/search.rst:132 +msgid "" +"A new filter rule can be added to the custom filter by clicking the " +":guilabel:`New Rule` button." +msgstr "" + +#: ../../content/applications/essentials/search.rst:134 +msgid "" +"Once the filter criteria are defined, click :guilabel:`Add` to add the " +"custom filter to the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:137 +msgid "" +"To target all leads and opportunities from the :menuselection:`CRM` app that" +" are in the *Won* stage, and have an expected revenue greater than $1,000, " +"the following should be entered:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:140 +msgid "" +":guilabel:`Match all` :icon:`fa-caret-down` :guilabel:`of the following " +"rules:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:142 +msgid ":guilabel:`Stage` :guilabel:`is in` :guilabel:`Won`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:143 +msgid ":guilabel:`Expected Revenue` :guilabel:`>` `1,000`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:144 +msgid ":guilabel:`any` :icon:`fa-caret-down` :guilabel:`of:`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:146 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Lead`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:147 +msgid ":guilabel:`Type` :guilabel:`=` :guilabel:`Opportunity`" +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Adding a custom filter to filter specific records in CRM." +msgstr "" + +#: ../../content/applications/essentials/search.rst:153 +msgid "" +"Activate :ref:`developer-mode` to reveal each field's technical name and " +"data type, as well as the :guilabel:`# Code editor` text area below the " +"filter rules, to view and edit the domain manually." +msgstr "" + +#: ../../content/applications/essentials/search.rst:160 +msgid "Group records" +msgstr "" + +#: ../../content/applications/essentials/search.rst:162 +msgid "" +"The display of records in a view can be clustered together, according to one" +" of the *preconfigured groups*. To do so, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select one of the " +":guilabel:`Group By` options from the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:167 +msgid "" +"To group the records by salesperson on the *Sales Analysis* report " +"(:menuselection:`Sales app --> Reporting --> Sales`), click the " +":guilabel:`Salesperson` option from the :guilabel:`Group By` drop-down menu." +" The view changes to group the records by salesperson, without filtering out" +" any records." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "Grouping records on the Sales Analysis report" +msgstr "" + +#: ../../content/applications/essentials/search.rst:175 +msgid "" +"It is possible to *customize groups* by using a field present on the model. " +"To do so, click :menuselection:`Add Custom Group`, and select a field from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/essentials/search.rst:179 +msgid "" +"Several groups can be used at the same time. The first group that is " +"selected is the main cluster, the next one that is added further divides the" +" main group's categories, and so on. Furthermore, filters and groups can be " +"used together to refine the view even more." +msgstr "" + +#: ../../content/applications/essentials/search.rst:186 +msgid "Comparison" +msgstr "" + +#: ../../content/applications/essentials/search.rst:188 +msgid "" +"Certain reporting dashboards include a :guilabel:`Comparison` section in the" +" drop-down menus of their search bars. This includes the :doc:`Overall " +"Equipment Effectiveness <../inventory_and_mrp/manufacturing/reporting/oee>` " +"report for the **Manufacturing** app and the :doc:`Purchase " +"<../inventory_and_mrp/purchase/advanced/analyze>` report for the " +"**Purchase** app, among others." +msgstr "" + +#: ../../content/applications/essentials/search.rst:194 +msgid "" +"The options in the :icon:`fa-adjust` :guilabel:`Comparison` section are used" +" to compare data from two different time periods. Pick between the two " +"comparison options: :guilabel:`(Time Filter): Previous Period` and " +":guilabel:`(Time Filter): Previous Year`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:201 +msgid "" +"For some reports, the :guilabel:`Comparison` section **only** appears in the" +" search bar drop-down" +msgstr "" + +#: ../../content/applications/essentials/search.rst:200 +msgid "" +"menu if one (or more) time periods have been selected in the " +":guilabel:`Filters` column. This is because there is nothing to compare if " +"no time period is specified." +msgstr "" + +#: ../../content/applications/essentials/search.rst:203 +msgid "" +"Additionally, some reports only allow use of the :guilabel:`Comparison` " +"feature when the :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` graph type or " +"the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view, is selected. A " +":guilabel:`Comparison` option can be selected even if another view is " +"enabled, but doing so does **not** change the way data is displayed on the " +"report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "The search bar for the production analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:212 +msgid "" +"To view data using one of the two comparisons, begin by selecting a time " +"period in the :guilabel:`Filters` column of the search bar drop-down menu. " +"Then, select either :guilabel:`(Time Filter): Previous Period` or " +":guilabel:`(Time Filter): Previous Year` in the :guilabel:`Comparison` " +"section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:217 +msgid "" +"With one of the :guilabel:`Comparison` options enabled, the report compares " +"the data for the selected period, with the data for the same unit of time " +"(month, quarter, year), one period or year prior. The way the data is " +"displayed depends on the selected view:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:221 +msgid "" +"The :icon:`fa-bar-chart` :guilabel:`(Bar Chart)` shows two bars, side-by-" +"side, for each unit of time for the selected time period. The left bar " +"represents the selected time period, while the right bar represents the " +"previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:224 +msgid "" +"The :icon:`fa-line-chart` :guilabel:`(Line Chart)` is displayed with two " +"lines, one representing the selected time period, and the other representing" +" the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:226 +msgid "" +"The :icon:`fa-pie-chart` :guilabel:`(Pie Chart)` appears as a large circle " +"with a smaller circle inside. The larger circle represents the selected time" +" period, while the smaller circle represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:229 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` is displayed with each column " +"split into two smaller columns. The right column represents the selected " +"time period, while the left column represents the previous time period." +msgstr "" + +#: ../../content/applications/essentials/search.rst:234 +msgid "" +"In the :guilabel:`Production Analysis` report of the " +":menuselection:`Manufacturing` app, data for the second quarter of 2024 is " +"compared to data for the second quarter of 2023. :guilabel:`Q2` is selected " +"in the :guilabel:`End Date` filter section of the search bar drop-down menu." +" In the :guilabel:`Comparison` section, :guilabel:`End Date: Previous Year` " +"is selected." +msgstr "" + +#: ../../content/applications/essentials/search.rst:239 +msgid "" +"The current year is 2024, so the larger circle shows data for the second " +"quarter (Q2) of 2024. The smaller circle shows data for the second quarter " +"(Q2) of 2023, which is the same time period, but one *year* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:243 +msgid "" +"If :guilabel:`End Date: Previous Period` is selected instead, the smaller " +"circle shows data for the first quarter (Q1) of 2024, which is the same time" +" period, but one *period* prior." +msgstr "" + +#: ../../content/applications/essentials/search.rst:0 +msgid "The comparison view of the Production Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:252 +msgid "Favorites" +msgstr "" + +#: ../../content/applications/essentials/search.rst:254 +msgid "" +"Favorites are a way to save a specific search for future use, or as the new " +"default filter for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:257 +msgid "" +"To save the current view as a favorite, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then select the " +":guilabel:`Save current search` drop-down menu to display the following " +"options:" +msgstr "" + +#: ../../content/applications/essentials/search.rst:261 +msgid ":guilabel:`Filter name`: Name of the favorited search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:262 +msgid "" +":guilabel:`Default filter`: Sets the favorited search as the default filter " +"for the view." +msgstr "" + +#: ../../content/applications/essentials/search.rst:263 +msgid "" +":guilabel:`Shared`: Makes the favorited search available to all users. " +"Otherwise, by default, the favorited search is only available to the user " +"who created it." +msgstr "" + +#: ../../content/applications/essentials/search.rst:266 +msgid "" +"Once the options are set, click :guilabel:`Save` to save the favorited " +"search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:-1 +msgid "Saving a favorite search on the Sales Analysis report." +msgstr "" + +#: ../../content/applications/essentials/search.rst:272 +msgid "" +"Favorited searches can be accessed by clicking the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then selecting the saved " +"search under :icon:`fa-star` :guilabel:`Favorites`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:276 +msgid "" +"Favorited searches that are only visible to the current user, i.e., that are" +" not shared, are shown first; any shared searches, whether created by the " +"current user or another user, are shown in a second section." +msgstr "" + +#: ../../content/applications/essentials/search.rst:280 +msgid "" +"To edit a favorited search, select the relevant saved search, hover over the" +" :icon:`fa-star` :guilabel:`(star)` icon beside the search name in the " +"search bar, then click the :icon:`fa-cog` :guilabel:`(cog)` icon. Modify the" +" conditions as needed, then click :guilabel:`Confirm`." +msgstr "" + +#: ../../content/applications/essentials/search.rst:284 +msgid "" +"To delete a favorited search, click the :icon:`fa-caret-down` " +":guilabel:`(dropdown)` icon in the search bar, then click the :icon:`fa-" +"trash` :guilabel:`(delete)` icon next to the saved search." +msgstr "" + +#: ../../content/applications/essentials/search.rst:288 +msgid "" +"To view *all* favorited searches, first activate :ref:`developer-mode`, and " +"navigate to :menuselection:`Settings app --> Technical --> User Interface: " +"User-defined Filters`. From here, all favorited searches can be viewed, " +"edited, archived, or deleted." +msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/hr.po b/locale/zh_CN/LC_MESSAGES/hr.po new file mode 100644 index 0000000000..e123e82505 --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/hr.po @@ -0,0 +1,33772 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/hr.rst:5 +msgid "Human resources" +msgstr "" + +#: ../../content/applications/hr/appraisals.rst:5 +msgid "Appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:3 +msgid "360 Feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:5 +msgid "" +"Odoo's **Appraisals** app lets managers gather feedback on their direct " +"reports from anyone in the company. Input from colleagues gives managers a " +"fuller view of each employee's strengths, growth areas, and collaboration " +"skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:12 +msgid "360 feedback dashboard" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:14 +msgid "" +"The :guilabel:`360 Feedback` section displays information for all the " +"surveys configured for the **Appraisals** app. To view the surveys and their" +" statistics, navigate to :menuselection:`Appraisals app --> Configuration " +"--> 360 Feedback`." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "A list view of all available surveys in the Appraisals application." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:21 +msgid "" +"Each appraisal, or survey, is presented on its own line on the " +":guilabel:`360 Feedback` dashboard, along with various information related " +"to that particular appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:24 +msgid "Each appraisal includes the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:26 +msgid ":guilabel:`Survey Name`: the name of the specific survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:27 +msgid "" +":guilabel:`Responsible`: the employee responsible for the survey, including " +"the month and year they were given that designation." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:29 +msgid "" +":guilabel:`Questions`: the number of questions in that particular survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:30 +msgid "" +":guilabel:`Average Duration`: the average time a user spends completing the " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:31 +msgid "" +":guilabel:`Registered`: the number of people who have been sent the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:32 +msgid "" +":guilabel:`Completed`: the number of people who have completed the survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:33 +msgid "" +":guilabel:`Certified`: if the survey is for a certification, the percentage " +"of users who have passed the certification." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:36 +msgid "Each appraisal row offers two actions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:38 +msgid "" +":guilabel:`Test`: Opens the appraisal in a new tab to preview the questions " +"without submitting answers. Close the tab to return to the list, or click " +":icon:`oi-arrow-right` :guilabel:`Go to Survey`/:guilabel:`Go to Appraisal` " +"for the full form." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:41 +msgid "" +":guilabel:`See Results`: :ref:`View response analytics `." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:46 +msgid "Request feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:48 +msgid "" +"To request feedback from a colleague, navigate to the **Appraisals** app, " +"and click on the appraisal card to open it." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:51 +msgid "" +"Click the :guilabel:`Ask Feedback` button, and an :guilabel:`Ask Feedback` " +"email pop-up window appears, using the :guilabel:`Appraisal: Ask Feedback` " +"email template." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:54 +msgid "" +"First, using the drop-down menu, select the employees being asked to provide" +" feedback in the :guilabel:`Recipients` field. Multiple employees may be " +"selected. Next, make any desired changes to the default message, and attach " +"any relevant documents." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:58 +msgid "" +"The :guilabel:`Answer Deadline` date is automatically set to the day after " +"the :guilabel:`Appraisal Date` on the appraisal form. Using the calendar " +"selector, modify the date, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:61 +msgid "" +"Click :guilabel:`Send`, and the feedback requests are sent to the specified " +"employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:-1 +msgid "The email pop-up when requesting feedback from other employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:69 +msgid "View results" +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:71 +msgid "" +"To view the results from everyone who has completed a survey, click the " +":guilabel:`See Results` button at the end of the corresponding survey line " +"in the :ref:`360 Feedback dashboard `. This " +"presents all the answers for the survey in a new tab. Each question provides" +" information on how many people responded to a question, and how many people" +" skipped it. All answers for each question are visible." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:77 +msgid "" +"To save a PDF version of the survey results, click the :icon:`fa-print` " +":guilabel:`(Print)` icon at the top of the page. To exit, close the tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:80 +msgid "" +"In addition to viewing the responses from past appraisals and surveys, new " +"surveys can also be created from the :guilabel:`360 Feedback` page. Click " +"the :guilabel:`New` button in the top-left of the page to create a new " +"survey." +msgstr "" + +#: ../../content/applications/hr/appraisals/360.rst:84 +msgid "" +"For more information on how to create a survey, refer to the " +":doc:`../../marketing/surveys/create` document." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:3 +msgid "Appraisal analysis" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:5 +msgid "" +"The **Appraisals** app has the ability to report on all the appraisals in " +"the system, including past, present, and future appraisals, and their " +"respective statuses. This report helps managers track scheduled appraisals, " +"and identify any overdue or unconfirmed ones." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:9 +msgid "" +"To access the *Appraisal Analysis* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Appraisal Analysis`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:12 +msgid "" +"On the :guilabel:`Appraisal Analysis` page, a report loads, displaying all " +"the appraisals in the database, in a default graph chart. Appraisals are " +"grouped by :guilabel:`Month`, then :guilabel:`Department`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:17 +msgid "View by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:19 +msgid "" +"Another way to view the *Appraisal Analysis* report is in the Gantt view, " +"which provides visual information on the appraisal's status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:22 +msgid "" +"Navigate to :menuselection:`Appraisals app --> Reporting --> Appraisal " +"Analysis`, and click the :icon:`fa-tasks` :guilabel:`(Gantt)` icon in the " +"upper-right corner. The report displays the current year, grouped by " +"department, with the current month highlighted." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:26 +msgid "" +"Each entry is highlighted in a different color to represent their status:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Color" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:29 +msgid "Meaning" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "Yellow" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid ":guilabel:`Done`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:31 +msgid "The appraisal was completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "Orange" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid ":guilabel:`Appraisal Sent`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:33 +msgid "The appraisal was confirmed, but not completed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "Red" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid ":guilabel:`Cancelled`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:35 +msgid "The appraisal was cancelled." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "Gray" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid ":guilabel:`To Start`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:37 +msgid "The appraisal was scheduled, but not confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:41 +msgid "" +"Appraisals are scheduled automatically (appear in gray), according to their " +"respective :ref:`appraisals/appraisal-plan`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:44 +msgid "" +"To change the period of time that is presented, adjust the date settings in " +"the top-left corner of the report by clicking the :icon:`fa-calendar` " +":guilabel:`From: (date) to (date)` to reveal a drop-down menu of options. " +"The options to display are :guilabel:`Today`, :guilabel:`This week`, " +":guilabel:`This month`, :guilabel:`This quarter`, and :guilabel:`This year`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:49 +msgid "" +"Additionally, a range of dates can be entered in the :guilabel:`From` and " +":guilabel:`To` fields at the bottom of the list, then click " +":guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:52 +msgid "" +"At any point, click the :icon:`fa-crosshairs` :guilabel:`(Focus Today)` " +"button to have the report include today's date in the view." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:55 +msgid "" +"To view the details of any appraisal, click on any appraisal. A pop-over " +"window appears, displaying the due date for the appraisal. To view more " +"details, click the :guilabel:`View` button, and further details appear in an" +" :guilabel:`Open` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:59 +msgid "" +"The report can have other :ref:`filters ` and " +":ref:`groupings ` set in the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals for the Appraisal Analysis report." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:68 +msgid "Group by status" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:70 +msgid "" +"When a company has a large number of employees, the default " +":guilabel:`Appraisal Analysis` report may display too much information to " +"view at one time. In this scenario, viewing the data by status can be " +"beneficial." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:74 +msgid "" +"First, clear any filters or groups from the search bar. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon in the far-" +"right of the search bar. Click :guilabel:`Status` in the :icon:`oi-group` " +":guilabel:`Group By` column. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:78 +msgid "" +"All the appraisals are now organized by status, in the following order: " +":guilabel:`Cancelled`, :guilabel:`Done`, :guilabel:`To Start`, and " +":guilabel:`Appraisal Sent`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:81 +msgid "" +"This view shows which appraisals need to be completed, and when, as well as " +"which appraisals still need to be confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A report showing all the appraisals, grouped by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:88 +msgid "Use case: view only the user's appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:90 +msgid "" +"When viewing the :guilabel:`Appraisal Analysis` report, it can save time to " +"only view the appraisals the signed-in user is responsible for, and hide the" +" rest." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:93 +msgid "" +"To only view this data, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the far-right of the search bar, revealing a drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:97 +msgid "" +"It is not necessary to remove the default :icon:`oi-group` " +":guilabel:`Department` grouping. If it remains active, the results are " +"grouped by department. If it is removed, the results appear in a list, " +"alphabetically." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:101 +msgid "" +"Click :guilabel:`Add Custom Filter` at the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, and a :guilabel:`Add Custom Filter` pop-up " +"window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:104 +msgid "" +"Click into the first field, and a pop-over appears with a variety of " +"options. Click the :icon:`fa-chevron-right` :guilabel:`(right arrow)` icon " +"after the word :guilabel:`Employee`, then scroll down and click on " +":guilabel:`Manager`. Next, set the middle field to :guilabel:`=` " +":guilabel:`(equal)`. Last, click the third field and select the desired user" +" from the list. When all the fields are set, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "A customized filter to show only the user's employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:113 +msgid "" +"Now, the only appraisals that appear are the appraisals that the selected " +"user is responsible for, instead of viewing *all* the appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:116 +msgid "" +"This report can also be :ref:`grouped by status `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:-1 +msgid "" +"A report showing only the appraisals the user is responsible for, by status." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:122 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:159 +msgid ":doc:`Odoo essentials reporting <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_analysis.rst:123 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:160 +msgid ":doc:`../../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:3 +msgid "Appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:8 +msgid "" +"The **Appraisals** app uses a preconfigured default template, which is " +"general enough to be applicable to all employees. If desired, the default " +"template :ref:`can be modified `, or, if " +"different templates are needed, such as department-specific appraisal " +"templates, new templates :ref:`can be created `." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:16 +msgid "Modify appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:18 +msgid "" +"If needed, changes can be made to the default template. To view the default " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:21 +msgid "" +"The default template appears in a list view, named :guilabel:`Default " +"Template`. Click on the template to view the template details. Make any " +"desired changes to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:24 +msgid "The default template consists of the following questions:" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:26 +msgid "Odoo **Appraisals** default appraisal template" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:29 +msgid "**Employee Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:30 +msgid "**Manager Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:33 +msgid "**My work**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:35 +msgid "**What are my best achievement(s) since my last appraisal?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:37 +msgid "" +"*Describe something that made you proud, a piece of work positive for the " +"company.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:39 +msgid "" +"**What has been the most challenging aspect of my work this past year and " +"why?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:41 +msgid "" +"*Did you face new difficulties? Did you confront yourself to new obstacles?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:43 +msgid "**What would I need to improve my work?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:45 +msgid "" +"*How can the company help you with your needs and objectives so you can " +"reach your goals and foster better collaboration.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:48 +msgid "**My future**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:50 +msgid "" +"**What are my short and long-term goals with the company, and for my " +"career?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:52 +msgid "*Give an example of a short-term objective (< 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:53 +msgid "*Give an example of a long-term objective (> 6 months)*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:55 +msgid "**Which parts of my job do I most / least enjoy?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:57 +msgid "" +"*Every job has strong points - which tasks do you enjoy the most and the " +"least?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:59 +msgid "**My feelings**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:61 +msgid "**How do I feel about the company...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:63 +msgid "Culture/Behavior: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:64 +msgid "Internal Communication: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:66 +msgid "**How do I feel about my own...**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:68 +msgid "Job content: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:69 +msgid "Work organization: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:70 +msgid "Remuneration: |5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:72 +msgid "**Feedback**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:74 +msgid "" +"**Give one positive achievement that convinced you of the employee's " +"value.**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:76 +msgid "" +"*Some achievements that illustrate their strengths in addressing job " +"challenges.*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:78 +msgid "**Evaluation**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +msgid "*Stress Resistance*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:81 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "|5-stars|" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:83 +msgid "*Time Management*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:85 +msgid "*Teamwork*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:87 +msgid "*Autonomy*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:89 +msgid "*Pro-activity*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:92 +msgid "**Improvements**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:94 +msgid "**How could the employee improve?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:96 +msgid "" +"*From a manager's point of view, how could you help them overcome their " +"weaknesses?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:98 +msgid "**Short term (6-months) actions / decisions / objectives**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:100 +msgid "*Do you need a rapid response to the current situation?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:102 +msgid "" +"**Long term (> 6 months) career discussion, where does the employee want to " +"go, how can you help them reach this path?**" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:105 +msgid "" +"*How do you see the employee's future - does your vision align with their " +"aspirations?*" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:110 +msgid "Create appraisal templates" +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:112 +msgid "" +"Large companies with many departments may prefer department-specific " +"appraisal templates, instead of using a default universal template. Creating" +" and using department-specific templates can be helpful if specific feedback" +" is needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:117 +msgid "" +"An appliance repair company has two main types of employees, office workers " +"who handle administrative tasks and scheduling, and repair technicians who " +"work in the field, performing repairs at customers' homes." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:121 +msgid "" +"This type of company may create two different appraisal templates, one for " +"the office workers, and one for the on-site repair technicians." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:124 +msgid "" +"To create a new appraisal template, click the :guilabel:`New` button in the " +"upper-left corner. Next, :doc:`configure the appraisal " +"<../../marketing/surveys/create>` by adding questions to the template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:127 +msgid "" +"Additionally, a new appraisal template can be created by duplicating the " +"default template, and making modifications to the copy. To duplicate the " +"template, navigate to :menuselection:`Appraisals app --> Configuration --> " +"Appraisal Templates`, then click on the template being duplicated. Click the" +" :icon:`fa-gear` :guilabel:`(Actions)` icon, then click :icon:`fa-clone` " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:132 +msgid "" +"First, change the name of the template, then make any desired changes to the" +" template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:135 +msgid "" +"Appraisal templates are housed in the **Surveys** app. Any appraisal " +"template created *in* the **Appraisals** app must be configured to be used " +"with the **Appraisals** app, or it will *not* be available for appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:139 +msgid "" +"To ensure a new template is available for the **Appraisals** app, navigate " +"to the **Surveys** app, and click on the appraisal template." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:142 +msgid "" +"Tick the radio button next to :guilabel:`Appraisal` at the top of the " +"survey. This setting allows the survey to be used in the **Appraisals** app," +" and is visible in the :guilabel:`Appraisal Template` drop-down menu." +msgstr "" + +#: ../../content/applications/hr/appraisals/appraisal_templates.rst:0 +msgid "" +"The appraisal radio button ticked on an appraisal form in the Surveys app." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:3 +msgid "Goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:5 +msgid "" +"The Odoo **Appraisals** application allows managers to set (and track) clear" +" goals for their employees. Continuous progress towards goals give employees" +" a concrete target between reviews, and give managers reliable insights when" +" evaluating performance." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:10 +msgid "View goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:12 +msgid "" +"To view all goals, navigate to :menuselection:`Appraisals app --> Goals`. " +"This presents all the goals for every employee, in a default list view, " +"grouped by :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:15 +msgid "" +"Click on an employee to expand the listed goals. Each goal displays the " +"following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:17 +msgid ":guilabel:`Name`: The name of the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:18 +msgid ":guilabel:`Created on`: The date the goal was made." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:19 +msgid "" +":guilabel:`Progress`: The percentage of progress the employee has achieved." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:20 +msgid ":guilabel:`Employee`: The employee assigned to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:23 +msgid "Only employees with goals assigned to them appear in the list." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A list of goals for all employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:31 +msgid "Create goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:33 +msgid "" +"To create new goals, navigate to :menuselection:`Appraisals app --> Goals`, " +"and click :guilabel:`New` in the top-left corner to open a blank goal form. " +"Add the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:37 +msgid ":guilabel:`Goal`: Type in a brief name for the goal in this field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:38 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"assigned the goal. Once this field is populated, the employee's manager " +"populates the :guilabel:`Manager` field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:40 +msgid "" +":guilabel:`Progress`: Click the current percentage of competency for the " +"goal. The options are :guilabel:`0%`, :guilabel:`25%`, :guilabel:`50%`, " +":guilabel:`75%`, or :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:42 +msgid "" +":guilabel:`Manager`: Using the drop-down menu, select the employee's manager" +" (if not already selected)." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:44 +msgid "" +":guilabel:`Deadline`: Using the calendar selector, enter the due date for " +"the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:45 +msgid "" +":guilabel:`Tags`: Using the drop-down menu, add any relevant :ref:`tags " +"` to the goal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:47 +msgid "" +":guilabel:`Description` tab: Enter any details regarding the goal in this " +"tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:50 +msgid "" +"Some goals can be broken down into steps, which may be input as a checklist." +" A checklist is a tool the employee may use to mark their progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:-1 +msgid "A completed goal created for learning Python." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:59 +msgid "Tags" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:61 +msgid "" +"Adding tags to goals can help when viewing the goals report, to see how many" +" goals with specific tags are assigned to employees." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:64 +msgid "" +"To view all the current tags, and add new ones, navigate to " +":menuselection:`Appraisals app --> Configuration --> Tags`. All tags appear " +"in a list view. The default tags are: :guilabel:`External`, :guilabel:`Hard " +"Skills`, :guilabel:`Internal`, :guilabel:`Programming`, :guilabel:`Soft " +"Skills`, and :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:69 +msgid "" +"To add a new tag, click the :guilabel:`New` button in the upper-left corner," +" and a new line appears at the bottom of the list. Enter the tag, then press" +" return or click away from the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:73 +msgid "Update goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:75 +msgid "" +"During employee appraisals, goals are reviewed to see how much progress the " +"employee has made. When an employee has achieved the next level of progress," +" the goal must be updated accordingly." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:78 +msgid "" +"To update a goal's progress percentage, navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:82 +msgid "" +"Click the new :guilabel:`Progress` box to set the new progress level. It is " +"recommended to add notes in the :guilabel:`Description` tab, as the employee" +" progresses with the goal. The notes should include dates the progress " +"changed, and any supporting information regarding the change." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:87 +msgid "" +"Goal progress can be updated at any time by the employee's manager, not only" +" during an appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:90 +msgid "Complete goals" +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:92 +msgid "" +"When a goal has been met, it is important to update the record. Navigate to " +":menuselection:`Appraisals app --> Goals`. Expand the employee whose goals " +"are being evaluated, and click on an individual goal to open the goal " +"record." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:96 +msgid "" +"Click the :guilabel:`Mark as Done` button in the upper-left corner. A green " +":guilabel:`Done` banner appears in the top-right corner of the goal card, " +"and the :guilabel:`Progress` changes to :guilabel:`100%`." +msgstr "" + +#: ../../content/applications/hr/appraisals/goals.rst:101 +msgid "" +"On the :guilabel:`Goals` dashboard, completed goals are indicated with a " +"green :guilabel:`100%` in the :guilabel:`Progress` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:3 +msgid "Conduct appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:5 +msgid "" +"This guide explains the end-to-end appraisal workflow in Odoo, from creation" +" to final rating, showing how managers and employees collaborate at each " +"stage." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:8 +msgid "" +":ref:`Employee self-assessment `: The employee" +" completes the Employee's Feedback template and updates their skills. " +"Responses remain hidden until the employee sets the form to *Visible to " +"Manager*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:11 +msgid "" +":ref:`Manager feedback `: While the employee " +"works on their section, the manager reviews goals, gathers peer input if " +"needed, and fills out the *Manager's Feedback* template. Feedback can remain" +" hidden until the appraisal meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:14 +msgid "" +":ref:`Appraisal review `: Manager and employee meet to " +"discuss both feedback sections, validate skill changes, and agree on next " +"steps. The meeting can be scheduled directly from the appraisal or the " +"calendar." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:17 +msgid "" +":ref:`Completion and rating `: After the discussion, " +"the manager assigns a final rating, adds any private notes, and marks the " +"appraisal Done. The record then locks unless it is reopened for further " +"edits." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:21 +msgid "" +"Throughout the process, optional actions, such as requesting peer feedback " +"or logging private manager notes, enhance the appraisal's accuracy and " +"relevance." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:27 +msgid "Employee self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:29 +msgid "" +"Once an appraisal is confirmed, the employee is required to fill out the " +"self-assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:32 +msgid "" +"Only confirmed appraisals can be worked on. If an appraisal is *not* " +"confirmed, the fields on the appraisal form cannot be edited, and feedback " +"cannot be recorded." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:35 +msgid "" +"After the employee receives a notification via email that an appraisal is " +"confirmed and scheduled, they are requested to fill out their half of the " +"default appraisal template, and update any skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:38 +msgid "" +"Employee's can click on the link in the confirmation email to navigate to " +"the appraisal, or they can open their appraisal in the **Appraisals** app. " +"To do this, open the **Appraisals** app, then click on the appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:42 +msgid "" +"The :guilabel:`Employee's Feedback` half of the template includes the " +"following sections: :guilabel:`My work`, :guilabel:`My future`, and " +":guilabel:`My feelings`. Each of these sections consists of several " +"questions for the employee to answer, allowing the employee to perform a " +"self-assessment, and provide feedback on how they feel about the company and" +" their role." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:48 +msgid "Employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:50 +msgid "" +"After completing the :ref:`Employee's Feedback ` section in the :guilabel:`Appraisal` tab, the employee next " +"updates their skills in the :guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:53 +msgid "" +"Any skills that were present on the employee's record when the appraisal was" +" confirmed, appear in this tab. If a :guilabel:`Skill Level` has changed " +"since the last appraisal, the level must be updated." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:58 +msgid "" +"The :guilabel:`Skills` tab does not appear on the appraisal until the " +"appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:60 +msgid "" +"Click on the :guilabel:`Skill Level` for the skill that has changed, " +"revealing a drop-down of all available levels. Click on the new level for " +"the skill. Once selected, the :guilabel:`Progress` field updates " +"accordingly. Next, click into the :guilabel:`Justification` field for the " +"skill, and enter any relevant details explaining the change. This field is " +"not necessary, but may aid management when reviewing the employee's skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:67 +msgid "Complete the self-assessment" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:69 +msgid "" +"The employee feedback remains hidden from management while the employee is " +"performing their self-assessment. Once the employee has completed their half" +" of the appraisal, and updated any skills, they tick the gray :guilabel:`Not" +" Visible to Manager` toggle. This changes the toggle text to " +":guilabel:`Visible to Manager`, the color changes to green, and their " +"responses are then visible to management." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:75 +msgid "" +"Additionally, a green dot appears on the appraisal card on the " +"**Appraisals** app dashboard, indicating the employee has completed their " +"assessment, and marked their half of the appraisal as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:82 +msgid "Manager feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:84 +msgid "" +"While the employee is completing their :guilabel:`Employee's Feedback` " +"section, the manager fills out the :guilabel:`Manager's Feedback` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:87 +msgid "" +"Before the manager fills out their portion of the appraisal, managers " +"typically review the employee's goals and skills, and ask for " +":ref:`additional feedback ` from the employee's " +"coworkers, to better understand all the achievements and challenges for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:91 +msgid "" +"Once the manager has all the information they need to evaluate the employee," +" they fill out the :guilabel:`Manager's Feedback` section of the appraisal " +"form. The manager's half has the following sections: :guilabel:`Feedback`, " +":guilabel:`Evaluation`, and :guilabel:`Improvements`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:95 +msgid "" +"The manager's appraisal focuses on the employee's accomplishments, as well " +"as identifying areas of improvements, with actionable steps to help the " +"employee achieve their goals in both the long and short term." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:99 +msgid "" +"When the feedback section is completed, the manager can tick the " +":guilabel:`Not Visible to Employee` toggle. This changes the toggle text to " +":guilabel:`Visible to Employee`, the color changes to green, and their " +"responses are then visible to the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:104 +msgid "" +"Some managers prefer to keep their feedback hidden from the employee until " +"they :ref:`meet with the employee ` to discuss the " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:110 +msgid "Ask for feedback" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:112 +msgid "" +"As part of the appraisal process, the manager can :ref:`request feedback for" +" an employee ` from anyone in the company " +"about an employee. In Odoo, this is referred to as *360 Feedback*." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:116 +msgid "" +"Feedback is requested from coworkers and anyone else who works with the " +"employee. This is to get a more well-rounded view of the employee, and aid " +"in the manager's overall assessment." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:120 +msgid "" +"To request feedback, the appraisal **must** be confirmed. Once confirmed, an" +" :guilabel:`Ask Feedback` button appears in the upper-left corner of the " +"form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:126 +msgid "Appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:128 +msgid "" +"Once both portions of an appraisal are completed (the :ref:`employee " +"` and :ref:`manager ` feedback sections), it is time for the employee and manager to " +":ref:`meet and discuss the appraisal `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:132 +msgid "" +"During the appraisal meeting, the manager reviews both the :ref:`Employee's " +"Feedback ` section as well as their own " +":ref:`Manager feedback `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:136 +msgid "" +"Additionally, the employee's :ref:`skills ` and " +":doc:`goals ` are reviewed at this time, and updated as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:142 +msgid "Schedule appraisal review" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:144 +msgid "" +"A meeting can be scheduled in one of two ways: either from the " +"**Appraisals** app dashboard, or from an individual appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:147 +msgid "" +"To schedule an appraisal from the dashboard of the **Appraisals** app, first" +" navigate to :menuselection:`Appraisals app --> Appraisals`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:150 +msgid "" +"Click the activity icon beneath the appraisal date on the desired appraisal " +"card, and an activity pop-up window appears. Click :icon:`fa-plus` " +":guilabel:`Schedule an activity`, and set the :guilabel:`Activity Type`` to " +":guilabel:`Meeting`. For more information on scheduling activities, refer to" +" the :ref:`activities documentation `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:155 +msgid "" +"Doing so opens a :guilabel:`New Event` pop-up form. From this pop-up form, " +"make any desired modifications, such as designating a :guilabel:`Start` " +"time." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:158 +msgid "" +"The employee populates the :guilabel:`Attendees` section by default. Add " +"anyone else who should be in the meeting, if necessary." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:161 +msgid "" +"To make the meeting a video call, instead of an in-person meeting, click " +":icon:`fa-plus` :guilabel:`Odoo meeting`, and a :guilabel:`Videocall URL` " +"link appears in the field." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:164 +msgid "" +"Once all the desired changes are complete, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:166 +msgid "" +"The meeting now appears on the calendar, and the invited parties are " +"informed, via email." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:-1 +msgid "" +"The meeting form with all information entered for Ronnie Hart's annual " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:171 +msgid "" +"The other way to schedule a meeting is from the individual appraisal form. " +"To do this, navigate to the :menuselection:`Appraisal app` dashboard, then " +"click on an appraisal card." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:174 +msgid "" +"Next, click on the :icon:`fa-calendar` :guilabel:`Meeting` smart button, and" +" the calendar loads. Follow the same directions above to create the meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:177 +msgid "" +"For more detailed information on how to schedule activities, refer to the " +":doc:`activities <../../essentials/activities>` documentation." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:181 +msgid "" +"If no meetings are scheduled, the :guilabel:`Meeting` smart button reads " +":guilabel:`No Meeting`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:186 +msgid "Review employee skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:188 +msgid "" +"Part of an appraisal is evaluating an employee's skills, and tracking their " +"progress over time. The :guilabel:`Skills` tab of the appraisal form auto-" +"populates with the skills from the :ref:`employee form `, " +"once an appraisal is confirmed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:192 +msgid "" +"Each skill is grouped with like skills, and the :guilabel:`Skill Level`, " +":guilabel:`Progress`, and :guilabel:`Justification` are displayed for each " +"skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:195 +msgid "" +":ref:`Update any skills, or add any new skills ` to the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:197 +msgid "" +"If a skill level has increased, enter a reason for the improved rating in " +"the :guilabel:`Justification` field, such as `took a fluency language test` " +"or `received Javascript certification`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:201 +msgid "" +"After an appraisal is completed, and the skills have been updated, the next " +"time an appraisal is confirmed, the updated skills populate the " +":guilabel:`Skills` tab." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:205 +msgid "" +"The :guilabel:`Skills` tab *can* be modified **after** the employee and " +"their manager have met and discussed the employee's appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:208 +msgid "" +"This is a common situation as the manager may not have all the necessary " +"information to assess and update the employee's skills before meeting." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:214 +msgid "Complete an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:216 +msgid "" +"After the appraisal has been filled out by both the employee and the " +"manager, and both parties have met and discussed the employee's performance," +" the manager then :ref:`logs any notes `, and " +":ref:`assigns a rating `." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:220 +msgid "" +"When completed, click the :guilabel:`Mark as Done` button in the upper-left " +"corner of the appraisal form." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:223 +msgid "" +"Once the appraisal is marked as *Done*, the status changes from " +":guilabel:`Confirmed` to :guilabel:`Done`, and the :guilabel:`Mark as Done` " +"button changes to a :guilabel:`Reopen` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:227 +msgid "" +"Modifications are **not** possible once the appraisal is marked as done." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:229 +msgid "" +"To make any changes to an appraisal with a status of :guilabel:`Done`, click" +" the :guilabel:`Reopen` button, then, click :guilabel:`Confirm`, and make " +"any modifications needed. Once all modifications are complete, click the " +":guilabel:`Mark as Done` button again." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:236 +msgid "Add a private note" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:238 +msgid "" +"Managers can log notes on an appraisal that are **only** visible to other " +"managers. Enter any notes in the :guilabel:`Private Note` tab. This can be " +"done anytime during the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:241 +msgid "" +"The employee being evaluated does **not** have access to this tab, and the " +"tab does **not** appear on their appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:244 +msgid "The tab is optional and does not affect the final rating." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:249 +msgid "Provide a final rating" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:251 +msgid "" +"After both the manager and employee have met to discuss the employee's " +"performance, the appraisal must be given a :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:254 +msgid "" +"Using the drop-down menu, select the rating for the employee. The default " +"options are: :guilabel:`Needs improvement`, :guilabel:`Meets expectations`, " +":guilabel:`Exceeds expectations`, :guilabel:`Strongly Exceeds Expectations`," +" and :guilabel:`Good`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:258 +msgid "" +"To add a new rating, navigate to :menuselection:`Appraisals app --> " +"Configuration --> Evaluation Scale`. The default ratings are presented in a " +"list view. To add a new rating, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the list. Enter" +" the new rating, then press the enter key, or click away from the line. Add " +"as many new ratings as needed." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:264 +msgid "" +"Click :menuselection:`Appraisals` in the top menu to return to the " +":guilabel:`Appraisals` dashboard, click on the appraisal, then select the " +"desired :guilabel:`Final Rating`." +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:268 +msgid ":doc:`../appraisals/goals`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:269 +msgid ":doc:`../appraisals/appraisal_analysis`" +msgstr "" + +#: ../../content/applications/hr/appraisals/new_appraisals.rst:270 +msgid ":doc:`../appraisals/skills_evolution`" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:3 +msgid "Schedule appraisals" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:5 +msgid "" +"Odoo's **Appraisals** app helps managers run recurring performance reviews. " +"Each review can include a self-assessment and can follow any schedule the " +"company sets." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:8 +msgid "" +"Regular appraisals turn day-to-day work into clear goals and measurable " +"skill targets. They also supply the objective evidence HR needs for raises " +"or promotions, and keep individual performance aligned with company KPIs." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:12 +msgid "" +"Reviews can be :ref:`scheduled automatically ` through an " +":ref:`appraisal plan ` that triggers evaluations " +"at set intervals, or :ref:`created manually ` whenever " +"needed—such as before a promotion or department transfer." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:19 +msgid "Automatic scheduling" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:21 +msgid "" +"To ensure no appraisal is missed, enable automatic scheduling by going to " +":menuselection:`Appraisals app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:24 +msgid "" +"The :guilabel:`Appraisals Plan` settings determines the frequency that " +"appraisals are scheduled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "" +"The appraisals sections with the timeline filled in and 360 feedback " +"enabled." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:32 +msgid "Appraisals plans" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:34 +msgid "" +"By default, appraisals are preconfigured to be automatically created six " +"months after an employee is hired, with a second appraisal exactly six " +"months after that." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:37 +msgid "" +"Once those two initial appraisals have been completed in the employee's " +"first year, following appraisals are only created once a year (every twelve " +"months)." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:40 +msgid "" +"To modify this schedule, change the number of months in the blank fields " +"under the :guilabel:`Appraisals Plans` section." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:44 +msgid "" +"Changing the :guilabel:`Appraisals Plans` field updates **every** employee " +"record whose :guilabel:`Next Appraisal Dates` is empty." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:48 +msgid "Appraisals automation" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:50 +msgid "" +"Tick the checkbox next to :guilabel:`Appraisals Automation` to have Odoo " +"automatically schedule *and* confirm appraisals." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:53 +msgid "" +"Appraisals are scheduled according to the :ref:`appraisal plan " +"`." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:58 +msgid "Manually schedule an appraisal" +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:60 +msgid "" +"Managers can schedule an appraisal at any time, outside the regular cycle." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:62 +msgid "" +"For example, if an employee is promoted, or transfers to a new role or a new" +" department, an appraisal is scheduled to assess performance in the current " +"role." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:65 +msgid "" +"To create a new appraisal, open the :menuselection:`Appraisals` app, and " +"click the :guilabel:`New` button in the upper-left corner. This opens a " +"blank :guilabel:`Appraisals` form." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:68 +msgid "" +"First, using the drop-down menu, select the employee being evaluated, in the" +" first field on the form. Once an employee is selected, the employee's " +":guilabel:`Manager`, :guilabel:`Job Position`, and :guilabel:`Department` " +"fields are populated according to the information on the employee record." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:72 +msgid "" +"The current date populates the :guilabel:`Appraisal Date` field, which is " +"the date the appraisal is scheduled to be completed. Using the calendar " +"selector, adjust the date, if desired. This field is typically updated when " +"the manager submits their final rating at the end of the appraisal process." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:76 +msgid "" +"If there is an :ref:`appraisal plan ` configured," +" the :guilabel:`Next Appraisal Date` field displays :guilabel:`Ongoing`. " +"This indicates that the following appraisal will be scheduled according to " +"the appraisal schedule. Once the appraisal is marked as complete, the " +":guilabel:`Next Appraisal Date` is updated with the date of the next " +"appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:81 +msgid "" +"Last, select the desired :guilabel:`Appraisal Template`. The " +":guilabel:`Default Template` populates this field, by default, and is " +"created when the **Appraisals** app is installed. Using the drop-down menu, " +"select a different template, if desired." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:85 +msgid "" +"Once the information in the top-half of the :guilabel:`Appraisals` form is " +"complete, click the :guilabel:`Confirm` button in the upper-left corner, and" +" the appraisal is scheduled, and the employee is notified." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:89 +msgid "" +"Once the appraisal is confirmed, both the employee and manager can start to " +"fill out the appraisal." +msgstr "" + +#: ../../content/applications/hr/appraisals/schedule_appraisals.rst:-1 +msgid "A new appraisal form with the top half filled out." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:3 +msgid "Skills evolution" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:5 +msgid "" +"In Odoo's **Appraisals** app, it is possible to view employee's skills as " +"they progress over time in the :ref:`Skills Evolution ` report, also known as the *Appraisal Skills Report*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:9 +msgid "" +"Managers can use this to see who is achieving their various skill goals set " +"on their appraisals, who is meeting their skill deadlines, who has the " +"highest performance in terms of skill development, and more." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:13 +msgid "" +"The *Skills Evolution* report also provides the ability to :ref:`search for " +"employees with specific skills ` at certain " +"levels, which can be helpful for scenarios where specific skills are " +"required." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:20 +msgid "Skills evolution report" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:22 +msgid "" +"To access this *Skills Evolution* report, navigate to " +":menuselection:`Appraisals app --> Reporting --> Skills Evolution`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:25 +msgid "" +"Doing so reveals the :guilabel:`Appraisal Skills Report` page. All skills " +"are grouped by the month they were created, then by employee, and then by " +"skill type." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:29 +msgid "" +"The :guilabel:`Appraisals Skills Report` only displays skills for employees " +"with at least one completed appraisal. Skills for employees whose appraisals" +" are still draft or pending are not included." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:33 +msgid "" +"When an employee completes their first appraisal, all their skills appear on" +" the report. Once subsequent appraisals are marked as done, any skill " +"changes from the previous appraisal appear on the report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:37 +msgid "" +"Any skill level changes from ongoing appraisals that have **not** been " +"finalized are **not** included in this report." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:40 +msgid "" +"To view the specific details for an employee's skill types, expand the " +":guilabel:`Employee`, then expand the individual :guilabel:`Skill Types`. " +"Each skill type displays the following information:" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:43 +#: ../../content/applications/hr/attendances.rst:239 +msgid ":guilabel:`Employee`: the name of the employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:44 +msgid ":guilabel:`Skill Type`: the category the skill falls under." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:45 +msgid ":guilabel:`Skill`: the specific, individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:46 +msgid "" +":guilabel:`Current Level`: the current level the employee has achieved for " +"the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:47 +msgid "" +":guilabel:`Previous Progress`: the previous percentage of competency " +"achieved for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:48 +msgid "" +":guilabel:`Current Progress`: the current percentage of competency achieved " +"for the skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:49 +msgid "" +":guilabel:`Justification`: any notes entered on the skill, explaining the " +"progress." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:51 +msgid "" +"The color of the skill text indicates any changes from the previous " +"appraisal. Skill levels that have increased since the last appraisal appear " +"in green, as an *Improvement*. Skill levels that have **not** changed appear" +" in black, as *No Change*. Skills that have regressed appear in red, as " +"*Regression*." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:56 +msgid "" +"This report can be modified to find specific information by adjusting the " +":ref:`filters ` and :ref:`groupings ` set in " +"the search bar at the top." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "A report showing all the skills grouped by employee." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:65 +msgid "Use case: Identify employees with specific skills" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:67 +msgid "" +"Since the :guilabel:`Appraisal Skills Report` organizes all skills by month," +" then employee, it can be difficult to find employees with a specific skill " +"at a specific level. To find these employees, a custom filter must be used." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:71 +msgid "" +"In this example, the report is modified to show employees with an expert " +"level of Javascript knowledge. To view only those employees, first remove " +"all active filters in the search bar." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:74 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon" +" in the search bar, then click :guilabel:`Add Custom Filter` beneath the " +":icon:`fa-filters` :guilabel:`Filters` column to load an :guilabel:`Add " +"Custom Filter` pop-up window." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:78 +msgid "" +"Using the drop-down menu in the first field, select :guilabel:`Skill`. Then," +" keep the second field as-is (:guilabel:`is in)`, and select " +":guilabel:`Javascript` from the third drop-down menu in the third field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:82 +msgid "" +"Next, click :guilabel:`New Rule`, and another line appears. In this second " +"line, select :guilabel:`Current Level` for the first drop-down field, leave " +"the second field as-is :guilabel:`(is in)`, then select :guilabel:`Expert` " +"for the third drop-down field." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:86 +msgid "" +"After the second rule is added, navigate to the text at the top of the pop-" +"up window that shows :guilabel:`Match any` :icon:`fa-caret-down` " +":guilabel:`of the following rules`. Click the drop-down menu for " +":guilabel:`any` and change it to :guilabel:`all`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:90 +msgid "Finally, click the :guilabel:`Add` button." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The Custom Filter pop-up with the parameters set." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:95 +msgid "" +"Now, only employees that have an :guilabel:`Expert` level for the skill " +":guilabel:`Javascript` appear. In this example, only :guilabel:`Marc Demo` " +"meets these criteria." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:-1 +msgid "The employees with expert Javascript skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:102 +msgid "Use case: Assess highest improvement" +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:104 +msgid "" +"Another way to modify the :guilabel:`Appraisal Skills Report` is to identify" +" the employee who has the highest amount of improved skills over a specific " +"period of time." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:107 +msgid "" +"To view this information, first remove the default filter in the search bar." +" Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` " +"icon in the search bar, then click :guilabel:`Improvement` beneath the " +":icon:`fa-filter` :guilabel:`Filters` column. Enabling this filter only " +"presents skills that have improved." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:112 +msgid "" +"It is possible to view the skills that have improved over a period of time, " +"such as a specific quarter, or month. With the search bar drop-down menu " +"still expanded, click :guilabel:`Add Custom Filter` at the bottom of the " +":icon:`fa-filter` :guilabel:`Filters` column, and an :guilabel:`Add Custom " +"Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:117 +msgid "" +"Select :guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Once :guilabel:`is " +"between` is selected, a second field appears after the last field. Using the" +" calendar selector, select the date range to apply the filter to. Once all " +"the fields are properly formatted, click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:122 +msgid "" +"The custom filter presents all skills that have been improved, organized by " +"employee, in a default list view." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:126 +msgid "" +"To determine the employee with the most amount of improved skills for the " +"second quarter, remove the default filter in the search bar of the " +":guilabel:`Appraisal Skills Report`. Next, activate the " +":guilabel:`Improvement` filter, then click :guilabel:`Add Custom Filter` at " +"the bottom of the :icon:`fa-filter` :guilabel:`Filters` column." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:131 +msgid "" +"In the resulting :guilabel:`Add Custom Filter` pop-up window, select " +":guilabel:`Create Date` for the first drop-down field, then select " +":guilabel:`is between` for the second drop-down field. Two date fields " +"appear after :guilabel:`is between` is selected." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:135 +msgid "" +"Using the calendar selector, set the first date to :guilabel:`04/01/2025` " +"and the second date to :guilabel:`06/30/2025`, then click :guilabel:`Add`." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:141 +msgid "" +"To view the number of employees and skills in further detail, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner to " +"view the data in a pivot table. This presents a pivot table with the " +"employees populating the rows, and the only visible column represents the " +"total number of improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:146 +msgid "" +"To expand the columns to view which skill types had the most overall " +"improvement, click :icon:`fa-plus-square` :guilabel:`Total` above the " +":guilabel:`Count` column, then click :guilabel:`Add Custom Group` :icon:`fa-" +"caret-down`, then click :guilabel:`Skill` from the resulting drop-down menu." +" This expands all the improved skills, organized by individual skill." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:152 +msgid "" +"In this example, :guilabel:`Audrey Peterson` improved the most in the third " +"quarter, with five improved skills." +msgstr "" + +#: ../../content/applications/hr/appraisals/skills_evolution.rst:0 +msgid "The pivot table showing the skill improvements for the third quarter." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:5 +msgid "Attendances" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:7 +msgid "" +"Odoo's **Attendances** application functions as a time clock. Employees are " +"able to check in and out of work using a :ref:`dedicated device in kiosk " +"mode `, while users are also able to check in " +"and out of work :ref:`directly from the database `. " +"Managers can see who is available at any given time, 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:17 +msgid "Access rights" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:19 +msgid "" +"Understanding access rights is essential to navigating the **Attendances** " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:21 +msgid "" +"Every user in the database is able to check in and out directly from the " +"database, without needing access to the **Attendances** app. Additionally, " +"all users can access their own attendance records from their employee form " +"in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:25 +msgid "" +"Access to both the **Attendances** application, and the various features " +"within the application is determined by access rights." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:28 +msgid "" +"To see what access rights a user has, navigate to the " +":menuselection:`Settings app --> 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 view the " +"settings. For the :guilabel:`Attendances` field, the options are either to " +"leave the field blank or select :guilabel:`Administrator`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:34 +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. If left blank, the user does **not** have access to the " +"**Attendances** application." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:40 +msgid "" +"If a user does **not** have :guilabel:`Administrator` rights for the " +"**Attendances** app, they are **not** able to open the app, even though it " +"appears on the main database dashboard. An :guilabel:`Access Error` pop-up " +"message appears, stating:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:44 +msgid "" +"`You do not have enough rights to access the fields " +"\"attendance_manager_id\" on Employee (hr.employee). Please contact your " +"system administrator.`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:47 +msgid "" +"Users who cannot access the **Attendances** app can still :doc:`check in and" +" check out <../hr/attendances/check_in_check_out>` of work within the " +"database, using the :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` that are always available at the top of " +"the database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:55 +msgid "Approvers" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:57 +msgid "" +"An approver is a user assigned to review and manage an employee's attendance" +" records. An approver is typically a manager, though that is not required. " +"Approvers without administrative rights can access and modify attendance " +"records **only** for the employees they are assigned to. This is the only " +"exception where non-admin users can view records in the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:62 +msgid "" +"To view who the attendances approver for an employee is, navigate to the " +":menuselection:`Employees application` and click on the specific employee. " +"Click on the :guilabel:`Work Information` tab, scroll to the " +":guilabel:`APPROVERS` section, and check the :guilabel:`Attendance` field. " +"The person selected is 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.rst:69 +#: ../../content/applications/hr/attendances/kiosks.rst:22 +#: ../../content/applications/hr/frontdesk.rst:15 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:840 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:956 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:10 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:16 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:12 +#: ../../content/applications/hr/time_off.rst:33 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:71 +msgid "" +"Few configurations are needed in the **Attendances** app. 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.rst:77 +msgid "" +"Any configuration item with an :icon:`fa-building-o` :guilabel:`(building)` " +"icon is a company-specific configuration. Items without an :icon:`fa-" +"building-o` :guilabel:`(building)` icon apply to all companies within the " +"database." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:84 +msgid "Modes" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:86 +msgid "" +":guilabel:`Attendances from Backend` :icon:`fa-building-o`: activate this " +"feature 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.rst:89 +msgid "" +":guilabel:`Automatic Check-Out` :icon:`fa-building-o`: activate this feature" +" to automatically check out employees according to their working schedule, " +"after a buffer of time has passed." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:91 +msgid "" +":guilabel:`Tolerance`: this field appears only when the :guilabel:`Automatic" +" Check-Out` :icon:`fa-building-o` feature is enabled. Enter the amount of " +"time, in hours, that must elapse after an employee's working hours have " +"ended, before they are automatically checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:96 +msgid "" +"With the :guilabel:`Automatic Check-Out` option enabled, and the " +":guilabel:`Tolerance` set to `2.00` hours, an employee checks in to work at " +"9:00 AM, and forgets to check-out at 5:00 PM. At 7:00 PM, they are " +"automaticlaly checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:100 +msgid "" +":guilabel:`Absence Management` :icon:`fa-building-o`: activate this feature " +"to log any absences that are not associated with a time off request, such as" +" vacation time or sick time, on the attendances report." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:105 +msgid "Extra Hours" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:107 +msgid "" +"This section specifies how extra time (sometimes referred to as *overtime*) " +"is calculated, including when extra time is counted and what time is not " +"logged." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:110 +msgid "" +":guilabel:`Tolerance Time In Favor Of Company`: enter the amount of time, in" +" minutes, that is **not** counted towards an employee's overtime. When an " +"employee checks out, and the extra time logged is below the specified " +"minutes, the extra time is **not** counted as overtime for the employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:114 +msgid "" +":guilabel:`Tolerance Time In Favor Of Employee`: enter the amount of time, " +"in minutes, that an employee is given, that does **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 are **not** penalized for their reduced hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:121 +msgid "" +"A company sets both of the :guilabel:`Tolerance` fields to `15` minutes, and" +" the working hours for the entire company are set from 9:00 AM to 5:00 PM." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:124 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:127 +msgid "" +"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 " +"are **not** penalized for this discrepancy." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:131 +msgid "" +":guilabel:`Extra Hours Validation` :icon:`fa-building-o`: tick either the " +"radio button next to :guilabel:`Automatically Approved` to have all extra " +"time automatically approved, or :guilabel:`Approved by Manager` if all extra" +" time should be reviewed and approved by a manager." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:135 +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/attendances.rst:139 +msgid "" +"Approved extra hours can be :ref:`deducted from an approved time off request" +" `." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:143 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:11 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:231 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:428 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:862 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1365 +#: ../../content/applications/hr/time_off.rst:527 +msgid "Overview" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:145 +msgid "" +"When entering the **Attendances** application, the :guilabel:`Overview` " +"dashboard is presented, containing all the user's check in and check out " +"information. If the user has the required :ref:`access rights " +"` or is an :ref:`approver " +"` for specific employees, those employeess' check-in " +"and check-out information also appears on the :guilabel:`Overview` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:151 +msgid "" +"The **Attendance** dashboard allows switching between :icon:`fa-tasks` " +":guilabel:`(Gantt)` and :icon:`oi-view-list` :guilabel:`(List)` views, and " +"selecting a period to analyze. The current period is automatically " +"highlighted in yellow for real-time attendance records, while the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button instantly returns the dashboard" +" to the present date." +msgstr "" + +#: ../../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/attendances.rst:162 +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 " +"employees with the errors." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:169 +msgid "Filters and groups" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:171 +msgid "" +"Sometimes, attendance officers and managers need to view specific records, " +"such as all automatic checkouts to determine which employees chronically " +"forget to check-out, or by department, to determine which team is working " +"the most overtime." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:175 +msgid "" +"For these cases, use the search bar to select a :icon:`fa-filter` " +":guilabel:`Filters` or :icon:`oi-group` :guilabel:`Group By`, or combine " +"these both to present the desired information." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:179 +msgid ":doc:`../essentials/search`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:182 +msgid "High-value filters" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:189 +msgid "Filter" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:190 +msgid "Common use case" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:191 +msgid "At Work" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:192 +msgid "" +"Verify employees still on-site before shutting down the building for the " +"night, or to perform a head count." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:194 +#: ../../content/applications/hr/lunch/orders.rst:86 +msgid "Errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:195 +msgid "View all errors to correct them prior to payroll processing." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:196 +msgid "Automatically Checked-Out" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:197 +msgid "" +"Perform an audit to determine employees who chronically forget to check-out " +"of work." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:198 +msgid "Date" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:199 +msgid "Limit results to a specific pay-period or audit window." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:200 +msgid "Active/Archived Employees" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:201 +msgid "" +"Switch between current staff and former employees when auditing historical " +"data." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:204 +msgid "Insightful groupings" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:211 +msgid "Group by" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:212 +msgid "When it helps" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:977 +msgid "Employee" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:214 +msgid "Review individual attendance records during a 1:1 meeting." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:215 +msgid "Department" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:216 +msgid "" +"Compare staffing levels and working hours to determine over-working and " +"under-working teams." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:217 +msgid "Manager" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:218 +msgid "" +"Determine where attendance follow-up questions can be directed to for an " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:219 +msgid "Method" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:220 +msgid "" +"Spot trends in attendance methods to potentially resolve hardware issues." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:221 +msgid "Date (Day/Week/Month)" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:222 +msgid "Identify absenteeism spikes or seasonal patterns." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:227 +msgid "Attendance log details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:229 +msgid "" +"Odoo records both the time and location for every check-in and check-out, " +"with fields varying by the method used. These detailed attendance logs can " +"confirm where an employee was on any given work day. This can be useful for " +"companies with hybrid working schedules, who may need to perform audits to " +"ensure proper compliance." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:234 +msgid "The detailed attendance log contains the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:237 +msgid "Main details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:240 +msgid ":guilabel:`Check In`: the date and time the employee checked in." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:241 +msgid "" +":guilabel:`Check Out`: the date and time the employee checked out. This " +"**only** appears if the employee has checked out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:243 +msgid "" +":guilabel:`Worked Time`: the total amount of time the employee logged for " +"the day, across multiple check-ins and outs. In an hour and minute format " +"(HH:MM)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:245 +msgid "" +":guilabel:`Worked Extra Hours`: unpaid overtime hours worked beyond the " +"expected working schedule (shows **only** when present for the employee)." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:247 +msgid "" +":guilabel:`Extra Hours`: approved overtime (the :guilabel:`Worked Time` " +"minus the approved :guilabel:`Worked Extra Hours`." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:251 +msgid "Check in/check out details" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:253 +msgid "" +"The following information appears for both the :guilabel:`Check In` and " +":guilabel:`Check Out` sections." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:256 +msgid "" +":guilabel:`Mode`: attendance submission method. Can be :ref:`Systray " +"`, :ref:`Kiosk `, or " +":guilabel:`Manual` entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:258 +msgid ":guilabel:`IP Address`: the device's IP address used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:259 +msgid "" +":guilabel:`Browser`: the web browser the employee used to log in or out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:260 +msgid "" +":guilabel:`Localisation`: the city and country associated with the " +"computer's IP address." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:261 +msgid "" +":guilabel:`GPS Coordinates`: the specific coordinates when the user logged " +"in or out. To view the specific coordinates on a map, click the :icon:`oi-" +"arrow-right` :guilabel:`View on Maps` button beneath the :guilabel:`GPS " +"Coordinates`. This opens a map in a new browser tab, with the specific " +"location pointed out." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:-1 +msgid "The detailed information for an attendance entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:270 +msgid "Attendance errors" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:272 +msgid "" +"Entries that contain an error appear on the overview dashboard in red. In " +"the :icon:`fa-tasks` :guilabel:`(Gantt)` view, the entry appears with a red " +"background. If in the :icon:`oi-view-list` :guilabel:`(List)` view, the " +"entry text appears in red." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:276 +msgid "" +"An error occurs when an employee has checked in but not checked out within " +"24 hours, or when a single check-in period exceeds 16 hours." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:279 +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/attendances.rst:286 +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/attendances.rst:289 +msgid "" +"To delete an entry, click the red :guilabel:`Delete` button on the pop-up " +"window instead of making modifications to the entry." +msgstr "" + +#: ../../content/applications/hr/attendances.rst:293 +msgid ":doc:`attendances/check_in_check_out`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:294 +msgid ":doc:`attendances/kiosks`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:295 +msgid ":doc:`attendances/management`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:296 +msgid ":doc:`attendances/hardware`" +msgstr "" + +#: ../../content/applications/hr/attendances.rst:297 +msgid ":doc:`attendances/attendance_reporting`" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:3 +msgid "Attendance reporting" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:5 +msgid "" +"The **Attendances** app report helps managers find attendance issues with " +"employees before they become a problem. The report can give insights on " +"trends by determining :ref:`which employees are working more overtime " +"`, and who is :ref:`not working their full shifts " +"`." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:11 +msgid "View report" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:13 +msgid "" +"To view the attendance report, click :guilabel:`Reporting` in the top menu. " +"The default report displays attendance information for current employees " +"over the past three months, in a default :icon:`oi-view-pivot` " +":guilabel:`Pivot table`. The rows are populated by employee, while the " +"columns are populated by the various attendance records. All entries are " +"grouped by month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:18 +msgid "The columns presented are:" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:20 +msgid "" +":guilabel:`Worked Hours`: The total logged time the employee worked for the " +"month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:21 +msgid "" +":guilabel:`Expected Hours`: The number of hours the employee should have " +"worked for the month, calculated from their :ref:`working schedule " +"`, configured on their employee form." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:24 +msgid "" +":guilabel:`Difference`: The difference from the :guilabel:`Expected Hours` " +"and the :guilabel:`Worked Hours` for the employee that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:26 +msgid "" +":guilabel:`Balance`: The difference between the *approved* overtime, and the" +" *total* overtime worked." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:29 +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/attendances/attendance_reporting.rst:-1 +msgid "" +"The default report view, with all the optional view buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:38 +msgid "Use case: monthly overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:40 +msgid "" +"Overtime affects a company's bottom line, as most companies budget for " +"employee salaries. When salaries exceed the expected amount, companies may " +"see a rise in overhead costs when salary budgets are exceeded. This is why " +"the attendance report is needed, to ensure no excessive overtime is logged." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:45 +msgid "" +"To view a specific month's overtime, by employee, click " +":guilabel:`Reporting` in the top menu of the **Attendances** app. Remove the" +" default :icon:`oi-group` :guilabel:`Date: Month > Employee` grouping in the" +" search bar. Click the :icon:`fa-caret-down` :guilabel:`(Toggle Search " +"Panel)` icon at the end of the search bar, then click :icon:`fa-caret-down` " +":guilabel:`Date`, and click the desired month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:50 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, and deselect :guilabel:`Expected Hours` and " +":guilabel:`Worked Hours`. This presents the :guilabel:`Difference` and " +":guilabel:`Balance` attendance data for the selected month, grouped by " +"employee." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:55 +msgid "" +"The :guilabel:`Difference` shows the month's total overtime logged, and the " +":guilabel:`Balance` shows the portion still unapproved. Click the " +":guilabel:`Difference` column to sort by the amount of overtime. The highest" +" positive number is the most overtime logged for that month." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:60 +msgid "" +"In the below example, a total of 38 hours and 53 minutes of overtime was " +"approved for the month of April. :guilabel:`Michael Williams` has the most " +"overtime, with 10 hours and 25 minutes logged. Of that overtime, only 25 " +"minutes was unapproved, for a total of ten paid overtime hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "The attendances report, showing only overtime for the month of April." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:70 +msgid "Use case: absenteeism" +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:72 +msgid "" +"Employees with a negative :guilabel:`Difference` indicate that they have not" +" worked their expected shifts. This can be from forgetting to log in and out" +" of work, or for working less hours than expected, without any approved time" +" off." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:76 +msgid "" +"To view the attendance data for the last three months, to identify any " +"trends, first open the **Attendances** app report. Next, click the " +":guilabel:`Measures` :icon:`fa-caret-down` button in the upper-left corner, " +"and ensure **only** :guilabel:`Difference` is selected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:80 +msgid "" +"Next, reset the row data by clicking :icon:`fa-minus-square-o` " +":guilabel:`Total` at the top of the rows. Then click :icon:`fa-plus-square` " +":guilabel:`Total` and select :guilabel:`Employee`. Click the " +":guilabel:`Difference` column name to sort by the total difference in logged" +" hours from the expected hours." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:85 +msgid "" +"The employee who worked the least has the highest negative balance. Click on" +" any of the numbers for the employee to view the detailed individual " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:89 +msgid "" +"In the below example, the company has only been opened for two months, so " +"data is only available for the last two months, even though the filter " +":guilabel:`Last 3 Months` is active." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:92 +msgid "" +"From this report, it is determined that :guilabel:`Abigail Peterson` worked " +"the least amount of hours over the past two months, working 25 hours less " +"than was expected." +msgstr "" + +#: ../../content/applications/hr/attendances/attendance_reporting.rst:0 +msgid "" +"The attendance report showing the highest absences for the last two months." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:3 +msgid "Check in and out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:5 +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 smaller companies, where every employee is" +" also a user, this feature may be useful." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:9 +msgid "" +"A user can check in and/or out on the main database Odoo dashboard, or while" +" inside any application. To do so, in the upper-right corner of the top main" +" header menu, which is always visible regardless of what application the " +"user is in, a :icon:`fa-circle` :guilabel:`(red circle)` or :icon:`fa-" +"circle` :guilabel:`(green circle)` is visible. Click on the colored circle " +"to reveal the attendance widget, enabling the user to check in or out." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:18 +msgid "Check in" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:20 +msgid "" +"If the attendance widget circle is red, this indicates the user is not " +"currently checked in. Click the :icon:`fa-circle` :guilabel:`(red circle)`, " +"and the attendance widget appears, displaying a green :guilabel:`Check in` " +":icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "Top right main menu with check in button highlighted." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:27 +msgid "" +"When the user checks in from the database, the **Attendances** app logs the " +"location details for the user, including the IP Address and GPS coordinates." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:31 +msgid "" +"For the **Attendances** app to log the location details, the user must allow" +" their computer to access their location information." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:34 +msgid "" +"If the user has not already checked in and out 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 in that field, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:39 +msgid "" +"Click the :guilabel:`Check in` :icon:`fa-sign-in` button to check in. The " +":icon:`fa-circle` :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` " +":icon:`fa-sign-in` button to a yellow :guilabel:`Check out` :icon:`fa-sign-" +"out` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:45 +msgid "Click anywhere on the screen to close the attendance widget." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:48 +#: ../../content/applications/hr/frontdesk/visitors.rst:175 +msgid "Check out" +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:50 +msgid "" +"If the user is checking out for the first time, :guilabel:`Since HH:MM " +"(AM/PM)` appears at the top of the widget, with the time the user checked in" +" populating the time field. Beneath that line, the hours and minutes that " +"have elapsed since checking in are displayed in a :guilabel:`HH:MM` format. " +"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/attendances/check_in_check_out.rst:56 +msgid "" +"If the user has previously checked in and out, additional fields are " +"presented. A :guilabel:`Before HH:MM (AM/PM)` field appears, in addition to " +"the :guilabel:`Since HH:MM (AM/PM)` field. The times displayed in both of " +"these fields match, and are populated with the most recent check in time. " +"Beneath the :guilabel:`Before HH:MM (AM/PM)` field, the previously logged " +"time is displayed, in an :guilabel:`HH:MM` (hours:minutes) format." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:62 +msgid "" +"In addition, beneath both of these fields, a :guilabel:`Total today` field " +"appears. This field is the sum of both the :guilabel:`Before HH:MM (AM/PM)` " +"and :guilabel:`Since HH:MM (AM/PM)` fields, and is the total time that is " +"logged for the user, if they were to log out at that moment." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:66 +msgid "" +"As time passes, both the :guilabel:`Since HH:MM (AM/PM)` and " +":guilabel:`Total today` fields are updated live. To check out, click the " +"yellow :guilabel:`Check out` :icon:`fa-sign-out` button. The attendance " +"widget updates again, displaying the :guilabel:`Total today` field with the " +"logged time, while the yellow :guilabel:`Check out` :icon:`fa-sign-out` " +"button changes to a green :guilabel:`Check in` :icon:`fa-sign-in` button." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:72 +msgid "" +"When the user checks out from the database, the **Attendances** app logs the" +" location details for the user. This information is logged **only** if the " +"user grants permission." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:-1 +msgid "" +"The pop-up that appears when an employee checks in inside the database." +msgstr "" + +#: ../../content/applications/hr/attendances/check_in_check_out.rst:79 +msgid "" +"The number of times a user can check in and check out is unlimited. Users " +"can 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 " +"main **Attendances** dashboard, including check-ins and check-outs with no " +"time value." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:3 +msgid "Hardware" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:5 +msgid "" +"Employees who are **not** database users, and therefore, do **not** have " +"access to the **Attendances** app, must sign in and out of work using a " +"kiosk. The following are the physical requirements for setting up a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:10 +msgid "Kiosk devices" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:12 +msgid "" +"A kiosk is a self-service station, where employees can :ref:`check in and " +"out of work ` with either a :ref:`badge " +"` or an :ref:`RFID key fob " +"`. Typically, these devices are dedicated as " +"kiosks only, but any device with an internet browser is able to be set up as" +" a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:17 +msgid "" +"A kiosk is used by navigating to the webpage specified in the " +":ref:`configuration ` section of the " +"**Attendances** app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:20 +msgid "Kiosks are set up using one of the following types of devices:" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:22 +msgid "Laptop or Desktop computer" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:23 +msgid "Tablet" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:24 +msgid "Mobile phone (Android or iOS)" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:27 +msgid "" +"Touchscreens are easy to use, and tablets and mobile phones take up less " +"space. That is why most consider using a smaller device with a touchscreen " +"as a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:30 +msgid "" +"It is recommended to place kiosks on a secure stand, or mount them securely " +"on a wall." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:35 +#: ../../content/applications/hr/employees/badges.rst:3 +msgid "Badges" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:37 +msgid "" +"Badges are a way for employees to quickly sign in and out from a kiosk, as " +"badges are scanned by the kiosk's camera to identify the employee." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:40 +msgid "" +"To generate a badge, first navigate to the :menuselection:`Employees app`. " +"Next, click on the desired employee card to open the employee's form, then " +"click the :guilabel:`Settings` tab." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:43 +msgid "" +"Under the :guilabel:`ATTENDANCE/POINT OF SALE/MANUFACTURING` section, there " +"is a :guilabel:`Badge ID` field. If this field is blank, click " +":guilabel:`Generate` at the end of the :guilabel:`Badge ID` line, and the " +"field is automatically populated with a new badge ID number. Then, click " +":guilabel:`Print Badge` at the end of the badge ID number to create a PDF " +"file of the badge." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:48 +msgid "" +"If a badge ID number is already present on the employee form, there is no " +":guilabel:`Generate` button, only a :guilabel:`Print Badge` button." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:51 +msgid "" +"The employee's badge contains the employee's photo, name, job position, " +"company logo, and a barcode that can be scanned at a kiosk to check in and " +"out." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:54 +msgid "" +"Badges can be printed for employees using any thermal or inkjet printer." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:-1 +msgid "A badge for an employee that is created from the Employees app." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:60 +msgid "" +"Badges are **not** required, as employees can manually identify themselves " +"on the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:63 +msgid "Barcode scanners" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:65 +msgid "" +"When using badges to check in and out, the barcode **must** be scanned to " +"identify the employee. This can be done with the kiosk's camera, if one is " +"available on the device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:68 +msgid "" +"If a camera is **not** available on the kiosk device, an external barcode " +"scanner must be used to scan badges." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:71 +msgid "" +"Kiosks work with most USB barcode scanners. Bluetooth barcode scanners are " +"also supported for devices without USB ports, or if a wireless connection is" +" desired." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:74 +msgid "" +"Follow the manufacturer's instructions on the barcode scanner to properly " +"connect the barcode scanner to the kiosk device." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:78 +msgid "" +"If the barcode scanner is connected directly to a computer, it :doc:`must be" +" configured <../../inventory_and_mrp/barcode/setup/hardware>` to use the " +"computer's keyboard layout." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:82 +msgid "An IoT box is **not** required to use a barcode scanner." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:87 +msgid "RFID key fob readers" +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:89 +msgid "" +"Instead of using a :ref:`badge `, employees can" +" scan a personal RFID key fob with an RFID reader to check in and out of " +"work." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:92 +msgid "" +"It is **required** to purchase *both* RFID key fobs and an RFID reader to " +"use this method to check in and out. Follow the manufacturer's directions to" +" install the RFID reader, and set up the RFID key fob." +msgstr "" + +#: ../../content/applications/hr/attendances/hardware.rst:97 +msgid "An IoT box is **not** required to use RFID key fobs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:3 +msgid "Kiosks" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:5 +msgid "" +"Odoo's **Attendances** app allows employees to check in and out of work " +"directly from the database or a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:8 +msgid "" +"A kiosk is a :doc:`dedicated device ` (a PC, tablet, or mobile " +"phone) for employees to use when they check in and out." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:11 +msgid "" +"Kiosks are needed for employees who do **not** have access to the database." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:13 +msgid "" +"Only employees with access to the Odoo database can check in and out from " +"the **Attendances** app, and they are referred to as *users*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:17 +msgid "" +"If employees :ref:`check in and out ` using a " +"badge or an RFID, then an :doc:`accessible device ` in :ref:`Kiosk" +" Mode ` **must** be available in order to use these " +"two methods." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:24 +msgid "" +"To use kiosks in the **Attendances** application, navigate to " +":menuselection:`Attendances app --> Configuration`. On the " +":guilabel:`Settings` page, configure the :ref:`Modes section " +"` and the :ref:`attendances/kiosk-settings`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:28 +msgid "" +"Once all desired settings have been configured, click the :guilabel:`Save` " +"button on the :guilabel:`Settings` page, to activate and enable them." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:34 +msgid "Modes section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:36 +msgid "" +"Determine how an employee checks in when using a kiosk, either by searching " +"for their name on the kiosk (:guilabel:`Manual Selection`), scanning an " +"employee ID or key fob (:guilabel:`Barcode/RFID`). or both." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:40 +msgid "" +"On the settings page, using the drop-down menu for the :guilabel:`Kiosk " +"Mode` :icon:`fa-building-o` field in the :guilabel:`Modes` section, make the" +" desired selection. Options are :guilabel:`Barcode/RFID`, " +":guilabel:`Barcode/RFID and Manual Selection`, or :guilabel:`Manual " +"Selection`." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:46 +msgid "" +"The **Barcode** application **does not** need to be installed to use one of " +"the Barcode/RFID settings." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:52 +msgid "Kiosk Settings section" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:54 +msgid "" +"The various settings in the :guilabel:`Kiosk Settings` section determine how" +" employees check in and out with kiosks." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:57 +msgid "" +":guilabel:`Barcode Source` :icon:`fa-building-o`: this setting **only** " +"appears if one of the two *Barcode/RFID* selections were configured for the " +":ref:`Kiosk Mode ` setting." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:61 +msgid "" +"If available, select how barcodes are scanned at the kiosk, via one of the " +"drop-down menu options. Barcodes can be scanned with a dedicated " +":guilabel:`Scanner`, or with a device's camera (:guilabel:`Front Camera` or " +":guilabel:`Back Camera`)." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:64 +msgid "" +":guilabel:`Display Time` :icon:`fa-building-o`: determine how many seconds a" +" check-in/check-out confirmation message remains on the kiosk screen before " +"returning to the main check in screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:66 +msgid "" +":guilabel:`Employee PIN Identification`: tick this checkbox if employees " +"should use a unique PIN to check in. PINs are configured on each individual " +"employee record. Refer to the :ref:`new employee documentation " +"` documentation for more information on setting up " +"PINs." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:70 +msgid "" +":guilabel:`Attendance Kiosk Url`: Odoo generates a unique web address (URL) " +"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** app kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:75 +msgid "" +"These kiosk URLs are **not** secured with any type of access code. Anyone " +"who has the URL can access the **Attendances** app kiosk. If the URL is " +"compromised for any reason, such as in the event of a security breach, click" +" :icon:`fa-refresh` :guilabel:`Generate new URL`, located beneath the link, " +"to generate a new URL, and update the kiosk, accordingly." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:81 +msgid "Kiosk mode" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:83 +msgid "" +"Entering *Kiosk Mode* is **only** available for users with specific " +":ref:`access rights `." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:86 +msgid "*Kiosk Mode* can be activated in two different ways:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:88 +msgid "" +"Navigate to the :menuselection:`Attendances app`, and click :guilabel:`Kiosk" +" Mode` in the top menu. The device then signs out of Odoo and enters *Kiosk " +"Mode*." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:90 +msgid "" +"Navigate to the :menuselection:`Attendances app --> Configuration`. In the " +":guilabel:`Kiosk Settings` section, use the link in the " +":guilabel:`Attendance Kiosk Url` field to open *Kiosk Mode* on any device." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "" +"The Attendances Kiosk URL field in the settings section of the Attendances " +"application." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:98 +msgid "" +"As a security measure, once a device is in *Kiosk Mode*, it is not possible " +"to go back into the database without signing back in." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:102 +msgid "" +"At any time, a new kiosk URL can be generated, if needed. Click the " +":icon:`fa-refresh` :guilabel:`Generate a new Kiosk Mode URL`" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:105 +msgid "" +"To exit *Kiosk Mode*, either close the tab in the web browser or return to " +"the main log-in screen of Odoo." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:111 +msgid "Check in and out with a kiosk" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:114 +msgid "Badge" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:116 +msgid "" +"To check in or out using a badge, tap the :icon:`fa-barcode` :guilabel:`Scan" +" your badge` image in the center of the kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:-1 +msgid "The Attendances Kiosk view displaying the scan badge image." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:122 +msgid "" +"Then, scan the barcode on the badge using the method configured in the " +":ref:`Kiosk Settings ` section of the " +"configuration menu." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:125 +msgid "" +"Once the barcode is scanned, the employee is checked in or out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:129 +msgid "RFID" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:131 +msgid "" +"To check in or out using an RFID key fob, scan the fob with an RFID reader." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:133 +msgid "" +"Once scanned, the employee is either checked in or checked out, and a " +":ref:`confirmation message ` appears with all the " +"information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:137 +msgid "Manually" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:139 +msgid "" +"Users who do not have a scannable badge, or an RFID fob, can manually check " +"in and out at a kiosk." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:141 +msgid "" +"Tap the :icon:`fa-user-o` :guilabel:`Identify Manually` button on the kiosk," +" and a screen appears with all the employees that can be checked in or out. " +"The **Employees** app dashboard has the same display." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:145 +msgid "" +"Tap on a person to check them in or out, and a :ref:`confirmation message " +"` appears." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:148 +msgid "To find a specific person, either:" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:150 +msgid "" +"Search: tap into the search bar and enter the desired person's name. As the " +"name is typed in, the matching results are displayed on the screen." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:152 +msgid "" +"By department: tap on any desired selection in the department section, " +"located on the left side of the screen, to **only** view employees from that" +" specific department. The number at the end of each listed department " +"represents how many employees that department has." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:157 +msgid "PIN" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:159 +msgid "" +"If the :guilabel:`Employee PIN Identification` checkbox was ticked 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/attendances/kiosks.rst:163 +msgid "" +"After the employee is selected, a number pad appears with a message. When " +"checking in, :guilabel:`(Employee) Please enter your PIN to check in` " +"appears above the numbers. When checking out, :guilabel:`(Employee) Please " +"enter your PIN to check out` appears above the numbers." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:167 +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/attendances/kiosks.rst:-1 +msgid "The pop-up that appears when prompted to enter a pin." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:176 +msgid "Confirmation message" +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:178 +msgid "" +"When an employee checks in or out, a confirmation message appears, with all " +"the check in or check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:181 +msgid "" +"When checking in, the :guilabel:`Welcome (Employee)` message appears, along " +"with the current date and time. If the employee has already checked in and " +"out that day, an :guilabel:`Hours Previously Today: HH:MM` message also " +"appears, showing the total hours logged earlier." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:185 +msgid "" +"When checking out, :guilabel:`Goodbye (Employee)` appears, as well as the " +"date and time of check out. Beneath the message is an :guilabel:`Hours " +"Today: HH:MM` field, with the total hours and minutes logged for the day." +msgstr "" + +#: ../../content/applications/hr/attendances/kiosks.rst:189 +msgid "" +"Beneath both the \"welcome\" and \"goodbye\" messages 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/attendances/kiosks.rst:-1 +msgid "The goodbye message with all the employee's check out information." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:3 +msgid "Work approvals and overtime" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:5 +msgid "" +"Odoo's **Attendances** app requires management oversight in order to ensure " +"all logged attendances are correct, especially overtime hours and incomplete" +" shifts." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:11 +msgid "Management dashboard" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:13 +msgid "" +"All attendance records that require approval, typically due to overlapping " +"work entries or unapproved time off, are managed from a centralized " +"management dashboard. To access this, navigate to " +":menuselection:`Attendances app --> Management`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:17 +msgid "" +"The :guilabel:`Management` dashboard only displays attendance records for " +"current employees that need to be approved, in a default list view. This is " +"due to the two default filters in the search bar, the :guilabel:`To Approve`" +" and :guilabel:`Active Employees`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:21 +msgid "Each attendance record displays the following information:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:23 +msgid ":guilabel:`Employee`: the name of the employee" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:24 +msgid ":guilabel:`Check In`: the date and time the employee checked in" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:25 +msgid ":guilabel:`Check Out`: the date and time the employee checked out" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:26 +msgid "" +":guilabel:`Worked Time`: the number of worked hours the employee logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:27 +msgid ":guilabel:`Worked Extra Hours`: the amount of overtime worked" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:28 +msgid ":guilabel:`Extra Hours`: the total extra hours logged" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:29 +msgid "" +":guilabel:`Overtime Status`: the status of the attendance record. All " +"attendance records that appear on this dashboard have a status of " +":guilabel:`To Approve`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"The Attendances app Management dashboard, displaying entries needing " +"approval." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:38 +msgid "Approvals and refusals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:40 +msgid "" +"Attendance records can be approved and refused directly from the " +":ref:`Management dashboard `. At the far-right of " +"each record, :icon:`fa-check` :guilabel:`Approve` and :icon:`fa-times` " +":guilabel:`Refuse` buttons appear. Click the corresponding button to either " +"approve or refuse the logged attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:46 +msgid "" +"When approving or refusing attendance records from the " +":guilabel:`Management` dashboard, it is **not** possible to view the details" +" of the attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:50 +msgid "Partial approvals" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:52 +msgid "" +"It is possible to approve a portion of the logged :guilabel:`Extra Hours` " +"and not the full amount. To approve only a portion of overtime, click into " +"an attendance record to view the details." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:55 +msgid "" +"Click into the :guilabel:`Extra Hours` field and enter the amount of hours " +"being approved. After editing the :guilabel:`Extra Hours field`, the " +":guilabel:`Worked Extra Hours` field becomes visible to display the " +"difference between the :guilabel:`Worked Time` and :guilabel:`Extra Hours` " +"fields." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:60 +msgid "" +"The :guilabel:`Worked Time` field is the total hours the employee logged " +"(the :guilabel:`Worked Time` and :guilabel:`Extra Hours` combined). For " +"example, if an employee is scheduled to work eight hours, and worked five " +"extra hours, the :guilabel:`Worked Time` is thirteen hours, and the " +":guilabel:`Extra Hours` is five hours. The :guilabel:`worked Time` field " +"**cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:65 +msgid "" +"Click :icon:`fa-check` :guilabel:`Approve` to approve the updated " +":guilabel:`Extra Hours`. Once partially approved, the :guilabel:`Worked " +"Extra Hours` field disappears, along with the :icon:`fa-check` " +":guilabel:`Approve` button. The difference in hours appears in the " +":guilabel:`Extra Hours` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:70 +msgid "" +"Once overtime hours are partially approved, the status changes to " +":guilabel:`Approved`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "A detailed attendance record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:76 +msgid "" +"Once partial overtime is approved, it is still possible to deny overtime by " +"clicking :icon:`fa-times` :guilabel:`Refuse`. The record can be modified as " +"many times as needed." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:80 +msgid "" +"Occasionally, verifying an employee's location when checking-in may be " +"needed. The method the employee checked-in to work is found on the " +"individual record, in the :guilabel:`Mode` field." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:83 +msgid "" +"The :guilabel:`Mode` field is not modifiable, as it only log the method the " +"attendance record was created." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:86 +msgid "The possible options are:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:88 +msgid "" +":guilabel:`Kiosk`: the employee physically checked in or out using a " +":doc:`kiosk ` device. The employee was present at the kiosk to " +"check-in." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:90 +msgid "" +":guilabel:`Systray`: the employee checked in or out :doc:`directly from the " +"database `. Depending on the :guilabel:`IP Address` " +"displayed on the detailed attendance record, the employee's location at the " +"time of check-in can be determined." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:93 +msgid "" +":guilabel:`Manual`: the record was created manually in the **Attendances** " +"app. This is typically done by management, to add a missing record." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:97 +msgid "Create attendance records" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:99 +msgid "" +"When necessary, users with the required :ref:`access rights ` are able to create attendance records manually in the " +"**Attendances** app. Some situations requiring this is when employees forget" +" to check in and out for shifts, as employees cannot retroactively create " +"attendance records." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:104 +msgid "" +"To add a missing attendance record, navigate to :menuselection:`Attendances " +"app --> Overview`. Click the :guilabel:`New` button in the upper-left " +"corner. In the :guilabel:`Create` pop-up window, enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:108 +msgid "" +":guilabel:`Employee`: select the employee the record is being created for. " +"The signed-in user populates this field, by default." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:110 +msgid "" +":guilabel:`Check In`: using the calendar modal, select the check in date and" +" time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"current date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:113 +msgid "" +":guilabel:`Check Out`: using the calendar modal, select the check out date " +"and time, then click :icon:`fa-check` :guilabel:`Apply`. By default, the " +"following date is selected, and the time is set to `00:00:00`." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:116 +msgid "" +":guilabel:`Worked Time`: this field is automatically populated with the " +"difference from the selected :guilabel:`Check In` and :guilabel:`Check Out` " +"times. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:118 +msgid "" +":guilabel:`Extra Hours`: enter the number of overtime hours, if any, to be " +"approved." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:121 +msgid "" +"Once :guilabel:`Extra Hours` are added, they are automatically approved by " +"the system. However, it is possible to manually refuse them, as explained in" +" the :ref:`Approvals and Refusals ` section." +msgstr "" + +#: ../../content/applications/hr/attendances/management.rst:-1 +msgid "" +"An Attendances app record form, filled out for Doris Cole for April 23, " +"2025." +msgstr "" + +#: ../../content/applications/hr/employees.rst:5 +#: ../../content/applications/hr/employees.rst:59 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:35 +msgid "Employees" +msgstr "" + +#: ../../content/applications/hr/employees.rst:7 +msgid "" +"Odoo **Employees** centralizes :doc:`personnel files " +"`, employment :doc:`contracts `, " +"and :doc:`departmental hierarchies ` in one system. " +"Properly configuring its settings ensures the dashboard shows each " +"employee's real-time attendance and work location—data that drives payroll " +"accuracy, capacity planning, and compliance reporting." +msgstr "" + +#: ../../content/applications/hr/employees.rst:53 +#: ../../content/applications/hr/fleet/new_vehicle.rst:16 +#: ../../content/applications/hr/lunch.rst:19 +#: ../../content/applications/hr/payroll.rst:15 +#: ../../content/applications/hr/recruitment.rst:31 +msgid "Settings" +msgstr "" + +#: ../../content/applications/hr/employees.rst:55 +msgid "" +"To view and configure the available settings, navigate to " +":menuselection:`Employees app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:61 +msgid "" +":guilabel:`Presence Display`: select how the employee's availability status " +"is calculated." +msgstr "" + +#: ../../content/applications/hr/employees.rst:63 +msgid "" +":guilabel:`Based on attendances`: marked available when :ref:`checked into " +"` the **Attendances** app." +msgstr "" + +#: ../../content/applications/hr/employees.rst:65 +msgid "" +":guilabel:`Based on user status in system`: marked available when the " +":doc:`employee logs in to Odoo `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:68 +msgid "" +":guilabel:`Advanced Presence Control`: when enabled, presence status can be " +"calculated from operational signals rather than check-ins or logins:" +msgstr "" + +#: ../../content/applications/hr/employees.rst:71 +msgid "" +":guilabel:`Based on number of emails sent`: an employee is marked present if" +" they send at least # emails per hour; otherwise, they are marked absent. " +"Enter the minimum number of emails that must be sent in the :guilabel:`Sent " +"Emails` field." +msgstr "" + +#: ../../content/applications/hr/employees.rst:74 +msgid "" +":guilabel:`Based on IP Address`: an employee is marked present only when " +"connected from one of the specified corporate IP addresses. Enter the IP " +"addresses in the :guilabel:`IP Addresses` field, separating each address " +"with a comma." +msgstr "" + +#: ../../content/applications/hr/employees.rst:78 +msgid "" +":guilabel:`Skills Management`: enable this option to display the " +":ref:`resumé tab ` on employee profiles. This allows for " +"the display of :ref:`work experience `, :ref:`skills " +"`, and :doc:`certifications `." +msgstr "" + +#: ../../content/applications/hr/employees.rst:81 +msgid "" +":guilabel:`Remote Work`: enable this option to allow for a detailed schedule" +" to appear on the employee form, in the :ref:`Work Information " +"` tab. When enabled, the specific location can be " +"set for each working day for the employee. The corresponding icon is " +"displayed in the upper-right corner of the employee card, indicating their " +"location by icon, and status by color." +msgstr "" + +#: ../../content/applications/hr/employees.rst:88 +msgid "" +"A green :icon:`fa-home` :guilabel:`(home)` icon indicates the employee is " +"working from home that day. A :icon:`fa-building` :guilabel:`(building)` " +"icon means the employee is scheduled to work at the office." +msgstr "" + +#: ../../content/applications/hr/employees.rst:92 +msgid "" +"The *color* of the icon indicates the employee's status, with green " +"indicating present, yellow indicating absent, and gray indicating it is " +"outside of the employee's working hours." +msgstr "" + +#: ../../content/applications/hr/employees.rst:0 +msgid "" +"Two employee Kanban cards displaying their working location and status." +msgstr "" + +#: ../../content/applications/hr/employees.rst:99 +msgid "Work organization" +msgstr "" + +#: ../../content/applications/hr/employees.rst:101 +msgid "" +"Using the drop-down menu, select the default :guilabel:`Company Working " +"Hours`. The default options are :guilabel:`Standard 40 hours/week`, " +":guilabel:`Appointment Resource Default Calendar`, and :guilabel:`Standard " +"32 hours/week (4 work days, friday free)`." +msgstr "" + +#: ../../content/applications/hr/employees.rst:105 +msgid "" +"The available working hours listed are the same as the configured " +":ref:`working schedules ` in the **Payroll** app. " +"Working hours can be created and modified from both the **Payroll** and " +"**Employees** apps." +msgstr "" + +#: ../../content/applications/hr/employees.rst:110 +msgid "Employee update rights" +msgstr "" + +#: ../../content/applications/hr/employees.rst:112 +msgid "" +"Enable the :guilabel:`Employee Editing` option to allow employees to edit " +"their own data on their employee record." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:5 +msgid "" +"In Odoo, employees can earn badges, either automatically through " +":doc:`challenges created in the CRM app " +"<../../sales/crm/optimize/gamification>`, through **eLearning** courses, or " +"manually, as managers decide to award them." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:9 +msgid "" +"Badges are a way to gamify the work day, can be created for any reason, and " +"can be granted to any user." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:13 +msgid "" +"Badges can **only** be awarded to :doc:`users of the database " +"<../../general/users>`, *and* if the **eLearning** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:17 +msgid "View available badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:19 +msgid "" +"To view the available badges that are configured by default, navigate to " +":menuselection:`Employees app --> Configuration --> Badges`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:22 +msgid "" +"All badges appear in a default Kanban view, with the badge's " +":guilabel:`Name` and image displayed. Additionally, the number of users " +"awarded the badge for both the current month, and in total, appears, along " +"with the badge description, and the avatar for each user who received the " +"badge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:26 +msgid "" +"Each badge has a :guilabel:`Grant` button to :ref:`award the badge " +"` from the :guilabel:`Badges` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "All the available badges, on the Badges dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:33 +msgid "Create badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:35 +msgid "" +"Badges can be created in the database when the default badges are not " +"sufficient. This can be done from the :guilabel:`Badges` dashboard in the " +"**Employees** app, or from the **CRM** app." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:38 +msgid "" +"To add a badge in the **Employees** app, first navigate to " +":menuselection:`Employees app --> Configuration --> Badges`, then click the " +":guilabel:`New` button in the upper-left corner." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:41 +msgid "" +"Fill out the badge form as outlined in the :ref:`CRM documentation " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:44 +msgid ":ref:`CRM Gamification `" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:47 +msgid "View employee badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:49 +msgid "" +"To view badges awarded to an employee, open the **Employees** app, and click" +" on an employee record. Click on the :guilabel:`Received Badges` tab to view" +" any awarded badges." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:53 +msgid "" +"If this tab is not visible, it means there is no :guilabel:`Related User` in" +" the :guilabel:`Settings` tab. Once a user is populated in the " +":guilabel:`Related User` field, the :guilabel:`Badges` tab appears." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:60 +msgid "Grant badges" +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:62 +msgid "" +"To grant a badge to an employee, open the employee record, and click into " +"the :guilabel:`Received Badges` tab. Click the :guilabel:`Grant a Badge` " +"button to load a :guilabel:`Reward Employee` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:66 +msgid "" +"Using the drop-down menu, select the badge being awarded in the " +":guilabel:`What are you thankful for?` field. The default options are " +":guilabel:`Good Job`, :guilabel:`Problem Solver`, and :guilabel:`Brilliant`." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:71 +msgid "" +"Additional options appear (e.g., :guilabel:`Get Started`, :guilabel:`Power " +"user`, :guilabel:`community Hero`) which are associated with challenges. " +"These are automatically granted through completed challenges. While these " +"can be awarded at any time, it is advised to grant badges manually that are " +"*not* associated with a challenge." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:76 +msgid "" +"Next, enter a brief summary of why the badge is being granted in the field " +"displaying :guilabel:`Describe what they did and why it matters (will be " +"public)` field. Last, click the :guilabel:`Reward Employee` button, and the " +"badge is awarded, and is visible in the :guilabel:`Badges` tab." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:82 +msgid "" +"Users cannot grant themselves badges. An error message appears if attempted." +msgstr "" + +#: ../../content/applications/hr/employees/badges.rst:-1 +msgid "The 'Reward Employee' field populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:3 +msgid "Certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:5 +msgid "" +"When jobs require specific knowledge, it is necessary to track employee " +"certifications to ensure the necessary knowledge and certifications are in " +"place." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:8 +msgid "" +"When jobs require specific knowledge, track employee certifications (e.g., " +"classes, tests, seminars) to verify required skills. Odoo accepts any " +"certification type without restriction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:12 +msgid "" +"To add certifications to an employee profile, and to access the *Employee " +"Certifications* report, the **Surveys** app **must** be installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:16 +msgid "View certifications" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:18 +msgid "" +"To view a full list of all employee certifications, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:21 +msgid "" +"All certifications appear in a list view, grouped by employee. Each " +"certification entry displays the following:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:24 +msgid "" +":guilabel:`Employee`: the employee's name, along with their avatar image." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:25 +msgid ":guilabel:`Name`: the title of the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:26 +msgid "" +":guilabel:`Validity Start`: when the employee received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:27 +msgid ":guilabel:`Validity End`: when the certification expires." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:28 +msgid "" +":guilabel:`Certification`: the corresponding course in the **Surveys** app " +"that was completed by the employee, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:31 +msgid "" +"The entries are also color-coded. Current certifications that are still " +"valid appear in black, expired certifications appear in red, and " +"certifications that are going to expire within the next 90 days appear in " +"orange." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:39 +msgid "" +"**Only** certification records with the *Display Type* set to " +"*Certification* on their :ref:`certification form ` appear on the :guilabel:`Employee Certifications` report. All other " +"certifications appear in the resume section of the :ref:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:45 +msgid "View certifications by expiration status" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:47 +msgid "" +"When managing a large number of employees with a variety of certifications, " +"it can be difficult to determine which employees need to keep necessary " +"certifications current in the default list view. In this scenario, it is " +"beneficial to view the certifications by expiration status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:51 +msgid "" +"To do so, navigate to :menuselection:`Employees app --> Reporting --> " +"Certifications`. Next, click the :icon:`fa-caret-down` :guilabel:`(Toggle " +"Search Panel)` icon in the search bar, then click :guilabel:`Add Custom " +"Group` :icon:`fa-caret-down`, revealing a drop-down menu. Click " +":guilabel:`Expiration Status`, then click away from the drop-down menu to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:56 +msgid "" +"After doing so, all the certifications are organized by status, starting " +"with :guilabel:`Expired` certifications, then certifications that are " +":guilabel:`Expiring` soon (within the next 90 days), and lastly, " +"certifications that are still :guilabel:`Valid`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:60 +msgid "" +"Filter certifications by expiration status to identify certifications " +"expiring soon, and identify employees who must renew." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "The list of employee certifications, grouped by status." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:69 +msgid "Log a certification" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:71 +msgid "" +"To log a certification for an employee, navigate to " +":menuselection:`Employees app --> Reporting --> Certifications`. Click " +":guilabel:`New`, and a blank certification form loads. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:75 +msgid "" +":guilabel:`Title`: Enter a short description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:76 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee who " +"received the certification." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:78 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the type of certification" +" received. This field determines where on the employee's resume the " +"certification appears. To create a new :guilabel:`Type`, enter the type in " +"the field, then click :guilabel:`Create [type]`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:82 +msgid "The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:84 +msgid "" +":guilabel:`Experience`: Select this option to have the certification appear " +"in the *Experience* section of the *Resume* tab on the :doc:`employee form " +"`. Experience entries are typically previous jobs or " +"internships." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:87 +msgid "" +":guilabel:`Education`: Select this option to have the certification appear " +"in the *Education* section of the *Resume* tab on the :doc:`employee form " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:89 +msgid "" +":guilabel:`Social Media`: Select this option to have the certification " +"appear in the *Social Media* section of the *Resume* tab on the " +":doc:`employee form `. Social Media entries typically relate " +"to certifications relating to digital marketing, social media management, " +"and specific trainings from social media platforms." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:93 +msgid "" +":guilabel:`Internal Certification`: Select this option to have the " +"certification appear in the *Internal Certification* section of the *Resume*" +" tab on the :doc:`employee form `. Internal certifications " +"entries are tied to courses, training, or programs created by the company, " +"that once completed, have a certification associated with it." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:97 +msgid "" +":guilabel:`Completed Internal Training`: Select this option to have the " +"certification appear in the *Completed Internal Training* section of the " +"*Resume* tab on the :doc:`employee form `. Completed internal " +"training entries are typically associated with trainings created by the " +"company, for company-specific processes. These do not result in any " +"certifications, but are logged on the employee profile to indicate completed" +" training." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:103 +msgid "" +":guilabel:`Display Type`: Select the visibility of the certification in this" +" field. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:106 +msgid "" +":guilabel:`Classic`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:108 +msgid "" +":guilabel:`Certification`: select this option to have the certification " +"appear in the *Resume* section of the employee form, **and** appear on the " +"*Employee Certifications* report. Once this is selected, a " +":guilabel:`Certification` field appears beneath the :guilabel:`Display Type`" +" field. Using the drop-down menu, select the corresponding **Surveys** app " +"certification the employee took. This field **only** appears if the " +"**Surveys** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:113 +msgid "" +":guilabel:`Course`: Select this option to have the certification appear in " +"the *Resume* section of the employee form, and **not** appear on the " +"*Employee Certifications* report. Once this option is selected, a " +":guilabel:`Course` field appears beneath the :guilabel:`Display Type` field." +" Using the drop-down menu, select the corresponding **eLearning** course the" +" employee took. This field **only** appears if the **eLearning** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:119 +msgid "" +":guilabel:`Description`: Enter a description for the certification in this " +"field." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:120 +msgid "" +":guilabel:`Duration`: Click into the first field, and a calendar pop-over " +"window appears. Click on the start and end dates for the certification " +"validity period. When the correct dates are selected, click :icon:`fa-check`" +" :guilabel:`Apply`, and both fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:-1 +msgid "" +"A certification form filled out for an OSHA certificate for construction." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:128 +msgid "" +"Once a certification is logged for an employee, a new certification of the " +"*same type* (i.e. :guilabel:`Education` or :guilabel:`Internal " +"Certification`) can be added directly from the employee form, instead of the" +" :guilabel:`Employee Certifications` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:132 +msgid "" +"In the main **Employees** app dashboard, click on an employee profile to " +"open their employee form. In the :guilabel:`RESUME` tab, click the " +":guilabel:`ADD` button at the end of the corresponding certification line." +msgstr "" + +#: ../../content/applications/hr/employees/certifications.rst:136 +msgid "" +"This :guilabel:`ADD` button **only** appears on employee profiles that " +"already have a certification." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:3 +msgid "Departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:5 +msgid "" +"All employees in the **Employees** app fall under specific departments " +"within a company." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:10 +msgid "Create new departments" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:12 +msgid "" +"To make a new department, navigate to :menuselection:`Employees app --> " +"Departments`, then click the :guilabel:`New` button in the top-left corner " +"to reveal a blank department form. Fill out the following information on the" +" department form:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:16 +msgid ":guilabel:`Department Name`: enter a name for the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:17 +msgid "" +":guilabel:`Manager`: using the drop-down menu, select the department " +"manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:18 +msgid "" +":guilabel:`Parent Department`: if the new department is housed within " +"another department (has a parent department), select the parent department " +"using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:20 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"department is part of. This field only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:22 +msgid "" +":guilabel:`Color`: select a color for the department. Click the colored box " +"to display all the color options. Click on a color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:24 +msgid "" +":guilabel:`Appraisal Templates`: using the drop-down menu, select the " +"appraisal form to be used for all employee appraisals within this " +"department. If a new appraisal is desired, enter the name for the appraisal," +" then click :guilabel:`Create and edit...` to modify the new appraisal form." +" This field **only** appears if the **Appraisals** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:28 +msgid "" +":guilabel:`Appraisal Survey`: using the drop-down menu, select the default " +"survey to use for the department when requesting feedback from employees " +"within the department. The default options are :guilabel:`Employee Opinion " +"Form`, :guilabel:`360 Feedback`, and :guilabel:`Employee Appraisal Form`. " +"This field **only** appears if the **Appraisals** app is installed, *and* " +"the *360 Feedback* option is enabled in the settings." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:34 +msgid "" +"After the form is completed, click the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon to manually save the changes. When saved, a " +":guilabel:`DEPARTMENT ORGANIZATION` chart appears in the top-right of the " +"department card, illustrating where the department lies in the organization." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The department for with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:42 +msgid "" +"The form auto-saves while data is entered, however the :guilabel:`Department" +" Organization` chart does **not** appear until the form is manually saved. " +"If the form is not saved, the :guilabel:`Department Organization` chart is " +"visible upon opening the department card from the :guilabel:`Departments` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:48 +msgid ":doc:`../appraisals`" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:51 +msgid "Departments dashboard" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:53 +msgid "" +"To view the currently configured departments, navigate to " +":menuselection:`Employees app --> Departments`. All departments appear in a " +"Kanban view, and are listed in alphabetical order." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:56 +msgid "" +"The default view for the :guilabel:`Departments` dashboard is a :ref:`Kanban" +" view `. It is possible to view the departments" +" in two other forms: a :ref:`list view ` and a " +":ref:`hierarchy view `." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "" +"The departments dashboard view with all the department cards in a Kanban " +"view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:67 +#: ../../content/applications/hr/fleet/accidents.rst:141 +#: ../../content/applications/hr/recruitment.rst:183 +msgid "Kanban view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:69 +msgid "" +"Each department has its own Kanban card on the main :guilabel:`Departments` " +"dashboard. Each department card displays the following information, if " +"available:" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:72 +msgid ":guilabel:`Name`: the name of the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:73 +msgid ":guilabel:`Manager`: the name and image of the department manager." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:74 +msgid "" +":guilabel:`Company`: the company the department is part of, including the " +"location icon." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:75 +msgid ":guilabel:`Employees`: the number of employees within the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:76 +msgid "" +":guilabel:`Appraisals`: the number of appraisals scheduled for employees in " +"the department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:77 +msgid "" +":guilabel:`Time Off Requests`: the number of unapproved time off requests " +"for employees in the department :ref:`awaiting approval ` . This **only** appears if there are requests to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:80 +msgid "" +":guilabel:`Allocation Requests`: the number of unapproved allocation " +"requests for employees in the department :ref:`awaiting approval " +"`. This **only** appears if there are requests " +"to approve." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:83 +msgid "" +":guilabel:`New Applicants`: the number of :ref:`new applicants " +"` for a position within the department. This **only** " +"appears if there are new applicants." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:85 +msgid "" +":guilabel:`Expense Reports`: the number of employees in the department with " +":doc:`open expense reports to approve " +"<../../finance/expenses/approve_expenses>`. This **only** appears if there " +"are any expense reports waiting for approval." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:88 +msgid "" +":guilabel:`Absence`: the number of employees with approved time off for the " +"current day." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:89 +msgid "" +"Color bar: the selected color for the department appears as a vertical bar " +"on the left side of the department card." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:93 +msgid "" +"Click on an alert in a department card, such as :guilabel:`Time Off " +"Requests`, to reveal a list view of the requests to approve for that " +"department" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:99 +msgid "List view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:101 +msgid "" +"To view the departments in a list view, click the :icon:`fa-align-justify` " +":guilabel:`(list)` icon in the top-right corner. The departments appear in a" +" list view, which displays the :guilabel:`Department Name`, " +":guilabel:`Company`, :guilabel:`Manager`, :guilabel:`Employees`, " +":guilabel:`Parent Department`, and :guilabel:`Color` for each department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:106 +msgid "" +"The departments are sorted alphabetically by :guilabel:`Department Name`, by" +" default." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a list view." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:114 +msgid "Hierarchy view" +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:116 +msgid "" +"To view the departments in a hierarchy view, click the :icon:`fa-share-alt " +"fa-rotate-90` :guilabel:`(Hierarchy)` icon in the top-right corner. The " +"departments appear in an organizational chart format, with the highest-level" +" department at the top (typically `Executive Management`), and all other " +"departments beneath it. All child departments of the first-level child " +"departments are folded." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:122 +msgid "" +"Each department card displays the :guilabel:`Department Name`, the " +":guilabel:`Manager` (and their profile image), the :guilabel:`Number of " +"Employees` in the department, and the number of any child departments." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:126 +msgid "" +"Click the :guilabel:`Unfold` button on a department card to expand it. Once " +"expanded, the :guilabel:`Unfold` button changes to a :guilabel:`Fold` " +"button. To collapse the department, click the :guilabel:`Fold` button. Only " +"**one** department *per row* can be unfolded at a time." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:130 +msgid "" +"Click anywhere on a department card to open the department form. Click the " +":guilabel:`(#) Employees` smart button to view a list of all the employees " +"in that department." +msgstr "" + +#: ../../content/applications/hr/employees/departments.rst:-1 +msgid "The departments presented in a hierarchy view." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:3 +msgid "Equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:5 +msgid "" +"Many employees are given various items to use while they work, such as " +"laptops, phones, and printers. Most companies track their equipment, to see " +"who is using what, as well as having a record of important information " +"regarding the equipment, such as serial numbers, warranty information, and " +"maintenance history." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:11 +msgid "" +"To track employee equipment, the **Maintenance** app *must* be installed." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:16 +msgid "Individual employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:18 +msgid "" +"Employee equipment is tracked on the employee record. To view all equipment " +"currently assigned to an employee, navigate to the " +":menuselection:`Employees` app, and click on the desired employee record." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:21 +msgid "" +"At the top of the record, an :icon:`fa-cubes` :guilabel:`Equipment Count` " +"smart button appears, with a number indicating how many, if any, items are " +"currently assigned to that employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:24 +msgid "" +"Click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button, and all" +" equipment currently assigned to the employee appears in individual Kanban " +"cards." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:27 +msgid "" +"Each Kanban card displays the equipment's name and model on the first line, " +"followed by the serial number (if available), and lastly, the employee's " +"name. Any current maintenance requests appear at the bottom of the card in a" +" red box." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for an employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:35 +msgid "A serial number is **not** required when logging equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:38 +msgid "All employee equipment" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:40 +msgid "" +"To view all equipment for all employees, start on the :ref:`equipment record" +" of an individual employee `." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:44 +msgid "" +"It does not matter what employee is selected, or whether they have any " +"equipment assigned to them. This step is only used to get to the " +":guilabel:`Equipment` list." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:47 +msgid "" +"In the Kanban view of the employee's equipment, clear the default " +":guilabel:`Assigned Employee` filter in the search bar. This presents *all* " +"equipment in the database, including those assigned to individual employees " +"and whole departments." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:51 +msgid "" +"Click into the search bar, and select :guilabel:`Employee` in the :icon:`oi-" +"group` :guilabel:`Group By` column. The equipment is now organized in a " +"Kanban view, by employee." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:54 +msgid "" +"In the Kanban view displaying all employee equipment records, equipment can " +"be reassigned by clicking and dragging an equipment card to the desired " +"employee. This changes ownership of the equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:-1 +msgid "A Kanban view of all equipment for all employees." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:62 +msgid "Add equipment to an employee record" +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:64 +msgid "" +"To add equipment to an employee's record, open the " +":menuselection:`Employees` app, click on the desired employee record, then " +"click the :icon:`fa-cubes` :guilabel:`Equipment Count` smart button at the " +"top." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:68 +msgid "" +"All equipment currently assigned to the employee appears in individual " +"Kanban cards. To add a new equipment record, click the :guilabel:`New` " +"button in the upper-left corner, and a blank :guilabel:`Equipment` form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:72 +msgid "" +":doc:`Fill out the equipment form " +"<../../inventory_and_mrp/maintenance/add_new_equipment>` for the employee's " +"equipment." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:76 +msgid "" +"Instead of filling out a new :guilabel:`Equipment` form for the same item, a" +" form can be duplicated, then updated." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:79 +msgid "" +"On the :guilabel:`Equipment` form, click the :icon:`fa-gear` " +":guilabel:`(Actions)` icon in the upper-left corner, then select :icon:`fa-" +"clone` :guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:82 +msgid "" +"An identical form appears, with *all* the information filled out, except for" +" the :guilabel:`Serial Number`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:85 +msgid "" +"Enter the :guilabel:`Serial Number` on the form, and make any other " +"necessary changes, such as the assigned :guilabel:`Employee`." +msgstr "" + +#: ../../content/applications/hr/employees/equipment.rst:0 +msgid "" +"A duplicate equipment form with all the information filled out except the " +"serial number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:3 +msgid "New employees" +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 " +"record. This record is a centralized place where all important information " +"about the employee is stored, including :ref:`general information " +"`, :ref:`job history and skills `," +" :ref:`various work information `, :ref:`personal " +"details `, :ref:`payroll-related information " +"`, and various :ref:`settings ` " +"that affect integrations with other apps in the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:13 +msgid "" +"To begin, open the :menuselection:`Employees` app, then click the " +":guilabel:`New` button in the upper-left corner. Doing so reveals a blank " +"employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:16 +msgid "" +"Proceed to fill out the required information, along with any additional " +"details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "Create a new employee form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:22 +msgid "" +"The current company phone number and name are populated in the " +":guilabel:`Work Phone` and :guilabel:`Company` fields. If the **Appraisals**" +" application is installed, the :guilabel:`Next Appraisal Date` field is " +"populated with a date six months from the current date." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:18 +msgid "General information" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:31 +msgid "Fill out the following employee details." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:34 +msgid "" +"The employee form automatically saves as data is entered. However, the form " +"can be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:37 +msgid "" +":guilabel:`Employee's Name`: enter the employee's name. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:38 +msgid "" +":guilabel:`Job Position`: this field appears below the employee name and can" +" be filled in manually. Alternatively, select a position from the drop-down " +"menu in the :guilabel:`Job Position` field beneath the " +":guilabel:`Department` field to auto-populate the top field. The two fields " +"do not need to match." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:44 +msgid "" +"While it is recommended to have the job positions match, the typed-in " +"description in this top field can contain more specific information than the" +" selected drop-down :guilabel:`Job Position`, if desired." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:48 +msgid "" +"For instance, if someone is hired for a sales representative position " +"configured as :guilabel:`Sales Representative` in the **Recruitment** app, " +"that can be selected in the drop-down :guilabel:`Job Position` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:52 +msgid "" +"In the typed-in :guilabel:`Job Position` field beneath the " +":guilabel:`Employee's Name`, the position can be more specific, such as " +"`Sales Representative - Subscriptions` if the employee is focused solely on " +"subscription sales." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "Both job position fields entered but with different information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:59 +msgid "" +":guilabel:`Photo`: in the top-right image box of the employee form, click on" +" the :icon:`fa-pencil` :guilabel:`(Edit)` icon, then select a photo to " +"upload." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:61 +msgid "" +"*Work Contact Information*: enter the employee's :guilabel:`Work Email`, " +":guilabel:`Work Phone`, and :guilabel:`Work Mobile`, information, if not " +"already auto-populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:63 +msgid "" +":guilabel:`Tags`: select a tag from the drop-down menu to add relevant tags " +"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 on an employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:66 +msgid "" +":guilabel:`Company`: from the drop-down menu in this field, select the " +"company the new employee was hired by, or create a new company by typing the" +" name in the field, and clicking :guilabel:`Create` or :guilabel:`Create and" +" edit...` from the mini drop-down menu that appears. This field is required." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:70 +msgid "" +":guilabel:`Department`: select the employee's department from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:71 +msgid "" +":guilabel:`Job Position`: select the employee's job position from the drop-" +"down menu. If using the **Recruitment** app, this list reflects configured " +"job positions. Once a selection is made, the :guilabel:`Job Position` field " +"beneath the :guilabel:`Employee's Name` field automatically updates to " +"reflect the currently selected job position, but is still editable." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:75 +msgid "" +":guilabel:`Manager`: select the employee's manager from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:76 +msgid "" +":guilabel:`Coach`: select the employee's coach from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:77 +msgid "" +":guilabel:`Next Appraisal Date`: this field is **only** visible if the " +"**Appraisals** application is installed. The 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/employees/new_employee.rst:83 +msgid "" +"After a :guilabel:`Department` is selected, the department's configured " +"manager and coach automatically populates the respective :guilabel:`Manager`" +" and :guilabel:`Coach` fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:87 +msgid "" +"To make edits to the selected :guilabel:`Department`, :guilabel:`Manager`, " +":guilabel:`Coach`, or :guilabel:`Company`, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` arrow next to the respective selection. The " +":icon:`oi-arrow-right` :guilabel:`(Internal link)` arrow opens the selected " +"form, allowing for modifications. Click :guilabel:`Save` after any edits are" +" made." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:95 +msgid "Resumé tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:98 +#: ../../content/applications/hr/payroll.rst:808 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:35 +msgid "Resumé" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:100 +msgid "" +"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/employees/new_employee.rst:106 +msgid ":guilabel:`Title`: type in the title of the previous work experience." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:107 +msgid ":guilabel:`Employee`: select the employee from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:108 +msgid "" +":guilabel:`Type`: from the drop-down menu, select either " +":guilabel:`Experience`, :guilabel:`Education`, :guilabel:`Social Media`, or " +":guilabel:`Internal Certification`. To create a new :guilabel:`Type`, enter " +"the name of the type, then click :guilabel:`Create \"(Type)\"`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:111 +msgid "" +":guilabel:`Display Type`: from the drop-down menu, choose " +":guilabel:`Classic` for typical work experience, or " +":guilabel:`Certification` for experience gained through a certification." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:113 +msgid "" +":guilabel:`Duration`: enter the start and end dates for the work experience." +" To select a date, click the first empty field to reveal a calendar pop-up " +"window. Proceed to use the :icon:`oi-chevron-left` :guilabel:`(left arrow)` " +"and :icon:`oi-chevron-right` :guilabel:`(right arrow)` icons to scroll to " +"the desired month, then click on the day to select it. Repeat this process " +"to locate and select the end date. When the desired dates have been " +"selected, click :icon:`fa-check` :guilabel:`Apply`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:119 +msgid ":guilabel:`Description`: enter any relevant details in this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:121 +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/employees/new_employee.rst:-1 +msgid "A resumé entry form with all the information populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:129 +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/employees/new_employee.rst:135 +msgid "Skills" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:137 +msgid "" +"An employee's skills can be entered in the :guilabel:`Resumé` tab in the " +"same manner that a resumé line is created." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:140 +msgid "" +"In order to add a skill to an employee record, the skill types must first be" +" configured. By default, Odoo comes with two :guilabel:`Skill Types` " +"preconfigured: *Languages* and *Soft Skills*. :ref:`Configure the rest of " +"the skill types ` before adding any skills to the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:145 +msgid "" +"When adding the first skill to an employee record, a :guilabel:`Pick a skill" +" from the list` button appears in the :guilabel:`Skills` section of the " +":guilabel:`Resumé` tab. Click the :guilabel:`Pick a skill from the list` " +"button, and select the following information for each skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:149 +msgid "" +":guilabel:`Skill Type`: select a :ref:`skill type ` " +"by clicking the radio button next to the skill type." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:151 +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 preconfigured " +"skill from the list." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:157 +msgid "" +"If the desired skill does not appear in the list, it is **not** possible to " +"add the new skill from this window. New skills must be added from the " +":ref:`Skill Types ` dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:161 +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 can be " +"created and modified from the :ref:`Skill Types ` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:166 +msgid "" +"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 add another skill." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:169 +msgid "" +"At any point, a new line can be added by clicking the :guilabel:`ADD` button" +" next to the corresponding section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:-1 +msgid "A skill form with the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:176 +msgid "" +"Only users with :guilabel:`Officer: Manage all employees` or " +":guilabel:`Administrator` rights for the **Employees** app can add or edit " +"skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:182 +msgid "Skill types" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:184 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:189 +msgid "" +"The default skill of :guilabel:`Languages` is preconfigured with twenty-one " +"skills, and the default :guilabel:`Soft Skills` is preconfigured with " +"fifteen skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:192 +msgid "" +"Click the :guilabel:`New` button in the upper-left corner, and a new " +":guilabel:`Skill Type` form appears. Fill out the following details for the " +"new skill type. Repeat this for all the needed skill types." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:196 +msgid "" +":guilabel:`Skill Type`: enter the name of the skill type. This acts as the " +"parent category for more specific skills and should be generic." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:198 +msgid "" +":guilabel:`SKILLS`: click :guilabel:`Add a line`, and enter the " +":guilabel:`Name` for the new skill, then repeat for all other needed skills." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:200 +msgid "" +":guilabel:`LEVELS`: click :guilabel:`Add a line`, and enter a " +":guilabel:`Name` and :guilabel:`Progress` percentage (`0`-`100`) for each " +"level." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:203 +msgid "" +"Set a :guilabel:`Default Level` by clicking the toggle on the desired line " +"(only one level can be selected). The toggle turns green to indicate the " +"default level. Typically, the lowest level is chosen, but any level can be " +"selected." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:206 +msgid "" +":guilabel:`DISPLAY`: click the colored box next to the :guilabel:`Color` " +"field to reveal a list of available colors for the skill type. Click on a " +"color to select it." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:210 +msgid "" +"To add a math skill set in yellow, enter `Math` in the :guilabel:`Name` " +"field. Then, in the :guilabel:`Skills` field, enter `Algebra`, `Calculus`, " +"and `Trigonometry`. Next, in the :guilabel:`Levels` field enter `Beginner`, " +"`Intermediate`, and `Expert`, with the :guilabel:`Progress` listed as `25`, " +"`50`, and `100`, respectively. Click :guilabel:`Set Default` on the " +"`Beginner` line to set this as the default skill level. Last, click the " +"colored box next to :guilabel:`Color`, and select yellow." +msgstr "" + +#: ../../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/employees/new_employee.rst:221 +msgid "" +"Once the form is completely filled out, click the :icon:`fa-cloud-upload` " +":guilabel:`(Save manually)` icon at the top of the screen, and the " +":guilabel:`Levels` rearrange in descending order, with the highest level at " +"the top, and the lowest at the bottom, regardless of the default level and " +"the order they were entered." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:229 +msgid "Work information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:231 +msgid "" +"The :guilabel:`Work Information` tab contains job-related details such as " +"the employee's schedule, roles, approvers (for time off, timesheets, and " +"expenses), remote work setup, and work location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:234 +msgid "" +"Click on the :guilabel:`Work Information` tab to access this section, and " +"enter the following information for the new employee, for the various " +"sections listed below." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:238 +msgid "LOCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:240 +msgid "" +"This section is visible for all employees, and does not require any other " +"apps to be installed for this section to be visible." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:243 +msgid "" +":guilabel:`Work Address`: select the :guilabel:`Work Address` from the drop-" +"down menu. The current company populates this field, by default. To modify " +"the address, hover over the first line (if there are multiple lines) of the " +"address to reveal an :icon:`oi-arrow-right` :guilabel:`(Internal Link)` " +"arrow. Click the :icon:`oi-arrow-right` :guilabel:`(Internal Link)` arrow to" +" open up the company form, and make any edits." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:249 +msgid "" +"Use the breadcrumb links to navigate back to the new employee form when " +"done." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:251 +msgid "" +"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/employees/new_employee.rst:254 +msgid "" +":guilabel:`Work Location`: using the drop-down menu, select where the " +":guilabel:`Work Address` is located. The default options are " +":guilabel:`Home`, :guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:257 +msgid "" +"To add a new location, type in the location name, then click " +":guilabel:`Create (new location)` to add the location, or :guilabel:`Create " +"and edit...` to add the location, assign a :guilabel:`Work Address`, and a " +":guilabel:`Cover Image`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:262 +msgid "APPROVERS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:264 +msgid "" +"To see this section, the user must have either :guilabel:`Administrator` or " +":guilabel:`Officer: Manage all employees` rights set for the **Employees** " +"application. For the category to appear, the respective app **must** be " +"installed. For example, if the **Time Off** app is not installed, the " +":guilabel:`Time Off` approver field does not appear. Only one selection can " +"be made for each field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:270 +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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:273 +msgid "" +"To check who has these rights, go to :menuselection:`Settings app` and click" +" :icon:`oi-arrow-right` :guilabel:`Manage Users` in the :guilabel:`Users` " +"section. Then, click on an employee, then click into the :guilabel:`Access " +"Rights` tab. Scroll to the :guilabel:`HUMAN RESOURCES` and check the various" +" settings." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:278 +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/employees/new_employee.rst:281 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Time Off`, " +"they **must** have either :guilabel:`Officer:Manage all Requests` or " +":guilabel:`Administrator` set for the :guilabel:`Time Off` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:284 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Timesheets`, " +"they **must** have either :guilabel:`Officer:Manage all contracts` or " +":guilabel:`Administrator` set for the :guilabel:`Payroll` role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:287 +msgid "" +"In order for the user to appear as an approver for :guilabel:`Attendances`, " +"they **must** have :guilabel:`Administrator` set for the :guilabel:`Payroll`" +" role." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:290 +msgid "" +":guilabel:`Expense`: using the drop-down menus, select the user responsible " +"for approving all expenses for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:292 +msgid "" +":guilabel:`Time Off`: using the drop-down menus, select the user responsible" +" for approving all time off requests from this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:294 +msgid "" +":guilabel:`Timesheet`: using the drop-down menus, select the user " +"responsible for approving all the employee's timesheet entries." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:296 +msgid "" +":guilabel:`Attendance`: using the drop-down menus, select the user " +"responsible for approving all attendance entries for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:300 +msgid "REMOTE WORK" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:302 +msgid "" +"This section **only** appears if the *Remote Work* setting is enabled in the" +" configuration menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:304 +msgid "" +"Use the drop-down menu to select the default location the employee works, " +"for each day of the week. The default options are :guilabel:`Home`, " +":guilabel:`Office`, or :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:307 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:310 +msgid "" +"After edits are done, click :guilabel:`Save & Close`, and the new location " +"is added, and populates the field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:313 +msgid "" +"Leave the field blank (:guilabel:`Unspecified`) for non-working days, such " +"as Saturday and Sunday." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:316 +msgid "" +"It is also possible to add or modify work locations by navigating to " +":menuselection:`Employees app --> Configuration --> Work Locations`. To " +"modify a location, click on an existing location, then make any changes on " +"the form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:320 +msgid "" +"Click :guilabel:`New` to create a new location, then enter the following " +"information on the form. All fields are **required**." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:323 +msgid "" +":guilabel:`Work Location`: enter the name for the location. This can be as " +"general or as specific, as needed, such as `Home` or `Building 1, Second " +"Floor`, respectfully." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:325 +msgid "" +":guilabel:`Work Address`: using the drop-down menu, select the address for " +"the location." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:326 +msgid "" +":guilabel:`Cover Image`: click on the icon to select it for the " +":guilabel:`Cover Image`. Options are a :icon:`fa-home` :guilabel:`(home)` " +"icon, an :icon:`fa-building-o` :guilabel:`(building)` icon, and a :icon:`fa-" +"map-marker` :guilabel:`(map marker)` icon." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:329 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the " +"location applies to. The current company populates this field, by default. " +"This field **only** appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "A new work location form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:339 +msgid "SCHEDULE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:341 +msgid "This section defines when the employee is expected to work." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:343 +msgid "" +":guilabel:`Working Hours`: using the drop-down menu, select the hours the " +"employee is expected to work. By default, a :guilabel:`Standard 40 " +"hour/week` working schedule is available. If the **Timesheets** app is " +"installed, an :guilabel:`Appointment Resource Default Calendar` option is " +"also available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:348 +msgid "" +"To view and modify the specific daily working hours, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal link)` arrow at the end of the " +":guilabel:`Working Hours` line. Working hours can be modified or deleted " +"here." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:353 +msgid "" +":guilabel:`Working Hours` are related to a company's working schedules, and " +"an Employee **cannot** have working hours that are outside of a company's " +"working schedule." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:356 +msgid "" +"Each individual working schedule is company-specific. For multi-company " +"databases, each company **must** have its own working hours set." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:359 +msgid "" +"If an employee's working hours are not configured as a working schedule for " +"the company, new working schedules can be added, or existing working " +"schedules can be modified." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:362 +msgid "" +"Working hours can be modified in the **Payroll** application, where they are" +" referred to as :guilabel:`Working Schedules`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:365 +msgid "" +"For more information on how to create or modify :guilabel:`Working " +"Schedules` in the **Payroll** application, refer to the " +":doc:`../../hr/payroll` documentation." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:368 +msgid "" +"After the new working time is created, or an existing one is modified, the " +":guilabel:`Working Hours` can be selected on the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:371 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the timezone for the " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:374 +msgid "PLANNING" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:376 +msgid "" +"This section is **only** visible if the **Planning** app is installed, as " +"this section affects what the employee can be assigned in the **Planning** " +"app." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:379 +msgid "" +":guilabel:`Roles`: using the drop-down menu, select all the roles the " +"employee can perform. There are no preconfigured roles available, so all " +"roles must be :ref:`configured in the Planning app `. There " +"is no limit to the number of roles assigned to an employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:382 +msgid "" +":guilabel:`Default Role`: using the drop-down menu, select the default role " +"the employee will typically perform. If the :guilabel:`Default Role` is " +"selected before the :guilabel:`Roles` field is configured, the selected role" +" is automatically added to the list of :guilabel:`Roles`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:389 +msgid "Private information tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:391 +msgid "" +"No information in the :guilabel:`Private Information` tab is required to " +"create an employee, however, some information in this section may be " +"necessary for the company's payroll department." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:394 +msgid "" +"In order to properly process payslips and ensure all deductions are " +"accounted for, it is recommended to check with the accounting department and" +" payroll department to ensure all required fields are populated." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:398 +msgid "" +"Enter the various information in the following sections and fields of the " +":guilabel:`Private Information` tab. Fields are entered either using a drop-" +"down menu, ticking a checkbox, or typing in the information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:403 +msgid "" +"Depending on the localization setting, other fields may be present. For " +"example, for the United States, a :guilabel:`SSN No` (Social Security " +"Number) field is present." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:407 +msgid "PRIVATE CONTACT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:409 +msgid "" +":guilabel:`Private Address`: enter the employee's private home address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:410 +msgid "" +":guilabel:`Private Email`: enter the employee's personal email address." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:411 +msgid ":guilabel:`Private Phone`: enter the employee's personal phone number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:412 +msgid "" +":guilabel:`Bank Account`: enter the bank account number for the employee, " +"and click :guilabel:`Create and edit..`. A :guilabel:`Create Bank Account` " +"form loads with the bank account number populating the :guilabel:`Account " +"Number` field. Next, select the :guilabel:`Bank` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:417 +msgid "" +"If the bank is not already configured, click :guilabel:`Create and edit...` " +"and a blank :guilabel:`Create Bank` form loads, with the bank name " +"populating the :guilabel:`Bank` field. Next, enter the :guilabel:`Bank " +"Identifier Code`, also referred to as a BIC or SWIFT code. Then enter the " +":guilabel:`Bank Address`, :guilabel:`Phone`, and :guilabel:`Email`. Once the" +" form is complete, click :guilabel:`Save & Close`, and the new bank " +"populates the :guilabel:`Bank` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:423 +msgid "" +"Next, enter the :guilabel:`ABA/Routing` number for the bank account, then " +"select the :guilabel:`Account Holder`, which is typically the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:426 +msgid "" +"Finally, click the :guilabel:`Send Money` toggle. This changes the toggle " +"color to green, and the status changes from :guilabel:`Untrusted` in black " +"text, to :guilabel:`Trusted` in green text." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:0 +msgid "The Create Bank Account form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:433 +msgid "" +"**All** bank accounts must be marked as :guilabel:`Trusted`, if not payments" +" cannot be processed and sent to the bank account. Having an " +":guilabel:`Untrusted` bank account for an employee will cause an error in " +"the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:437 +msgid "" +":guilabel:`Home-Work Distance`: enter the number, in miles or kilometers, " +"the employee commutes to work, in one direction. The unit of measure can be " +"changed from kilometers (:guilabel:`km`) to miles (:guilabel:`mi`) using the" +" drop-down menu. This field is only necessary if the employee is receiving " +"any type of commuter benefits or tax deductions based on commute distances." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:441 +msgid "" +":guilabel:`Private Car Plate`: enter the license plate for the employee's " +"personal car." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:444 +msgid "EMERGENCY" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:446 +msgid "" +"This section details the person to contact in the event of an emergency." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:448 +msgid ":guilabel:`Contact Name`: enter the emergency contact's name." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:449 +msgid "" +":guilabel:`Contact Phone`: enter the emergency contact's phone number. It is" +" recommended to enter a phone number that the person has the most access to," +" typically a mobile phone." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:453 +msgid "FAMILY STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:455 +msgid "" +"This section is used for tax purposes, and affects the **Payroll** app. " +"Enter the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:458 +msgid "" +":guilabel:`Marital Status`: select the marital status for the employee using" +" the drop-down menu. The default options are :guilabel:`Single`, " +":guilabel:`Married`, :guilabel:`Legal Cohabitant`, :guilabel:`Widower`, and " +":guilabel:`Divorced`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:462 +msgid "" +"If :guilabel:`Married` or :guilabel:`Legal Cohabitant` is selected, two " +"additional fields appear: :guilabel:`Spouse Complete Name` and " +":guilabel:`Spouse Birthdate`. Enter these fields with the respective " +"information." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:465 +msgid "" +":guilabel:`Number of Dependent Children`: enter the number of dependent " +"children. This number is the same number used for calculating tax " +"deductions, and should follow all tax regulations regarding applicable " +"dependents." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:470 +msgid "CITIZENSHIP" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:472 +msgid "" +"This section outlines all the information relating to the employee's " +"citizenship. This section is primarily for employees who are working in a " +"different country than their citizenship. For employees working outside of " +"their home country, for example on a work visa, this information may be " +"required. Information for all fields may not be available." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:477 +msgid "" +":guilabel:`Nationality (Country)`: using the drop-down menu, select the " +"country the employee is from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:479 +msgid "" +":guilabel:`Identification No`: enter the employee's identification number in" +" this field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:480 +msgid ":guilabel:`SSN No`: enter the employee's social security number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:481 +msgid ":guilabel:`Passport No`: enter the employee's passport number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:482 +msgid "" +":guilabel:`Gender`: select the employee's gender from the drop-down menu. " +"The default options are :guilabel:`Male`, :guilabel:`Female`, and " +":guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:484 +msgid "" +":guilabel:`Date of Birth`: using the calendar selector, select the birthday " +"of the employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:485 +msgid "" +":guilabel:`Place of Birth`: enter the city or town the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:486 +msgid "" +":guilabel:`Country of Birth`: using the drop-down menu, select the country " +"the employee was born." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:487 +msgid "" +":guilabel:`Non-resident`: tick this checkbox if the employee lives in a " +"foreign country." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:490 +msgid "EDUCATION" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:492 +msgid "" +"This section allows for only one entry, and should be populated with the " +"highest degree the employee has earned." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:495 +msgid "" +":guilabel:`Certificate Level`: using the drop-down menu, select the highest " +"degree the employee has earned. The default options are " +":guilabel:`Graduate`, :guilabel:`Bachelor`, :guilabel:`Master`, " +":guilabel:`Doctor`, and :guilabel:`Other`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:498 +msgid "" +":guilabel:`Field of Study`: type in the subject the employee studied, such " +"as `Business` or `Computer Science`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:500 +msgid "" +":guilabel:`School`: type in the name of the school the employee earned the " +"degree from." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:503 +msgid "WORK PERMIT" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:505 +msgid "" +"This section should be filled in if the employee is working on some type of " +"work permit. This section may be left blank if they do not require any work " +"permits for employment." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:508 +msgid ":guilabel:`Visa No`: enter the employee's visa number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:509 +msgid ":guilabel:`Work Permit No`: enter the employee's work permit number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:510 +msgid "" +":guilabel:`Visa Expiration Date`: using the calendar selector, select the " +"date the employee's visa expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:512 +msgid "" +":guilabel:`Work Permit Expiration Date`: using the calendar selector, select" +" the date the employee's work permit expires." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:514 +msgid "" +":guilabel:`Work Permit`: click :guilabel:`Upload your file`, then navigate " +"to the work permit file in the file explorer, and click :guilabel:`Select` " +"to add the permit." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:520 +msgid "Payroll tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:522 +msgid "" +"Depending on the installed :doc:`localization " +"<../payroll/payroll_localizations>`, the sections and fields in this tab may" +" vary considerably. Due to the specific nature of localizations and the " +"variety of information that may be requested in this tab, it is recommended " +"to check with the accounting department to fill out this section correctly." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:527 +msgid "The following fields are universal for all localizations:" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:529 +msgid "" +":guilabel:`Legal Name`: enter the legal name for the employee. This is the " +"name that typically is used for filing taxes." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:531 +msgid "" +":guilabel:`Payslip Language`: enter the desired language to be used when " +"printing payslips for this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:533 +msgid "" +":guilabel:`Registration Number of the Employee`: enter the employees " +"registration number." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:536 +msgid ":doc:`Payroll localizations <../payroll/payroll_localizations>`" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:541 +msgid "Settings tab" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:543 +msgid "" +"This tab provides various fields for different applications within the " +"database. Depending on what applications are installed, different fields may" +" appear in this tab." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:547 +msgid "STATUS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:549 +msgid "" +":guilabel:`Employee Type`: using the drop-down menu, select the *type* of " +"employee. The default options are :guilabel:`Employee`, :guilabel:`Worker`, " +":guilabel:`Student`, :guilabel:`Trainee`, :guilabel:`Contractor`, and " +":guilabel:`Freelancer`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:552 +msgid "" +":guilabel:`Related User`: using the drop-down menu, select a user in the " +"database to link to this employee." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:556 +msgid "Employees do **not** need to be users of the database." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:558 +msgid "" +"*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." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:561 +msgid "" +"After the employee is created, click :guilabel:`Create User` at the end of " +"the :guilabel:`Related User` line. A :guilabel:`Create User` form appears." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:564 +msgid "" +"The employee name populates the :guilabel:`Name` field by default. If the " +":guilabel:`Email Address`, :guilabel:`Phone`, :guilabel:`Mobile`, and " +":guilabel:`photo` are populated on the employee form, the corresponding " +"fields are auto-populated on the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:568 +msgid "" +"Once the form is completed, click the :guilabel:`Save` button. The user is " +"created, and populates the :guilabel:`Related User` field." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:571 +msgid "" +"Users can also be created manually. For more information on how to manually " +"add a user, refer to the :doc:`../../general/users/` document." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:575 +msgid "APPLICATION SETTINGS" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:577 +msgid "" +"This section affects the **Fleet** and **Manufacturing** apps. Enter the " +"following information in this section." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:580 +msgid "" +":guilabel:`Hourly Cost`: enter the hourly cost for the employee, in a XX.XX " +"format. This cost is factored in when the employee is working at a " +":doc:`work center " +"<../../inventory_and_mrp/manufacturing/advanced_configuration/using_work_centers>`." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:585 +msgid "" +"Manufacturing costs are added to the costs for producing a product, if the " +"value of the manufactured product is **not** a fixed amount. This cost does " +"**not** affect the **Payroll** application." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:589 +msgid "" +":guilabel:`Fleet Mobility Card`: if applicable, enter the :guilabel:`Fleet " +"Mobility Card` number" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:592 +msgid "ATTENDANCE/POINT OF SALE" +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:594 +msgid "" +"This section determines how employees sign in to either the **Attendances** " +"or **Point Of Sale** apps, and only appear if either of these apps is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:597 +msgid "" +":guilabel:`PIN Code`: enter the employee's pin number in this field. This " +"code is used to sign in and out of **Attendances** app kiosks, and a " +":abbr:`POS (Point Of Sale)` system." +msgstr "" + +#: ../../content/applications/hr/employees/new_employee.rst:599 +msgid "" +":guilabel:`Badge ID`: click :guilabel:`Generate` at the end of the " +":guilabel:`Badge ID` line to create a badge number. Once generated, the " +"badge number populates the :guilabel:`Badge ID` field, and " +":guilabel:`Generate` changes to :guilabel:`Print Badge`. Click " +":guilabel:`Print Badge` to create a PDF file of the employee's badge. The " +"badge can be printed and used to log into a :abbr:`POS (point of sale)` " +"system or :ref:`check-in ` on an " +"**Attendances** app kiosk." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:3 +msgid "Offboarding" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:5 +msgid "" +"When an employee leaves the company, it is important to have an " +":ref:`offboarding plan ` to ensure all necessary " +"steps are followed, such as returning equipment, revoking access to business" +" systems, filling out HR forms, having an exit interview, and more. " +"Depending on the company, there could be several different offboarding " +"plans, configured for specific departments or divisions, that have different" +" requirements and steps from the main offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:12 +msgid "" +"In addition to an offboarding plan, the employee record must be " +":ref:`updated to reflect their departure `, log the " +"reason why they left, close any open activities associated with the " +"employee, and :ref:`provide them with any important documents " +"`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:19 +msgid "View offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:21 +msgid "" +"Before offboarding can begin, it is recommended to check the default " +"offboarding plan that comes preconfigured with the **Employees** app. To " +"view the current default plan, navigate to :menuselection:`Employees app -->" +" Configuration --> Activity Plan`. Click :guilabel:`Offboarding` to view the" +" detailed offboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:27 +msgid "Offboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:29 +msgid "" +"The default :guilabel:`Offboarding` plan is minimal, with two default steps " +"(three if the **Fleet** app is installed). All steps are :guilabel:`To-Do` " +"activities, and are scheduled for the day the offboarding plan is launched " +"(:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:33 +msgid "" +":guilabel:`Organize knowledge transfer inside the team`: The manager must " +"ensure all knowledge the employee has relating to their job position, is " +"either documented or shared with colleagues so there is no knowledge gap." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:36 +msgid "" +":guilabel:`Take Back Fleet`: The fleet manager ensures any vehicles assigned" +" to the employee are either unassigned (available for other employees) or " +"the next driver is assigned. This step only appears if the **Fleet** app is " +"installed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:39 +msgid "" +":guilabel:`Take Back HR Materials`: The manager must obtain any documents " +"and materials the HR department requires. It is recommended to check with " +"the HR department to ensure everything required for this step is completed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The three default steps in the Offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:47 +msgid "Modify offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:49 +msgid "" +"The default offboarding plan is minimal, so that modifications can be made " +"to accommodate any company's offboarding needs. Every company has different " +"requirements, therefore it is necessary to add the required steps to the " +"offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:53 +msgid "" +"If the offboarding plan is universal, add or modify the default offboarding " +"plan. If the offboarding plan needed is only for a specific department, then" +" a new plan should be created, specifically for that department." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:57 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Offboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:60 +msgid "" +"To modify a step, click on the step and an :guilabel:`Open: Activities` pop-" +"up window appears. Make any desired modifications to the step, then click " +":guilabel:`Save` to accept the changes and close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:64 +#: ../../content/applications/hr/employees/onboarding.rst:103 +msgid "" +"To add a new step, click :guilabel:`Add a line` at the bottom of the listed " +"activities in the :guilabel:`Activities To Create` tab, and a blank " +":guilabel:`Create Activities` pop-up window appears. Enter all the " +"information in the pop-up window, then click :guilabel:`Save & Close` if " +"there are no other steps to add, or click :guilabel:`Save & New` if more " +"steps are needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:69 +msgid "Configure all the desired steps for the offboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:72 +msgid "Create offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:74 +msgid "" +"For some companies, specific offboarding plans may be necessary for some " +"departments. For these cases, a new department-specific offboarding plan may" +" be needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:77 +msgid "" +"To create a new offboarding plan, first navigate to " +":menuselection:`Employees app --> Configuration --> Activity Plan`. Click " +"the :guilabel:`New` button in the upper-left corner, and a blank plan form " +"loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:81 +#: ../../content/applications/hr/fleet/accidents.rst:48 +#: ../../content/applications/hr/frontdesk.rst:35 +#: ../../content/applications/hr/lunch/products.rst:12 +#: ../../content/applications/hr/payroll.rst:828 +#: ../../content/applications/hr/payroll/work_entries.rst:56 +#: ../../content/applications/hr/time_off.rst:250 +msgid "Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:83 +msgid ":guilabel:`Plan Name`: the specific name for the plan." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:84 +msgid "" +":guilabel:`Model`: This field specifies where this plan can be used. In this" +" case, in the **Employees** app. This field is not able to be modified." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:86 +msgid "" +":guilabel:`Department`: if left blank (the default setting) the plan is " +"available for all departments. To make the plan department-specific, select " +"a department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:89 +msgid "" +"Next, add the various steps for the plan by clicking :guilabel:`Add a line` " +"at the bottom of the listed activities in the :guilabel:`Activities To " +"Create` tab, and a blank :guilabel:`Create Activities` pop-up window " +"appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:93 +msgid "Enter the following information in the pop-up window:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:95 +msgid "" +":guilabel:`Activity Type`: Using the drop-down menu, select the specific " +"activity to be scheduled. The default options are :guilabel:`Email`, " +":guilabel:`Call`, :guilabel:`Meeting`, :guilabel:`To-Do`, or " +":guilabel:`Upload Document`. If the **Sign** app is installed, a " +":guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:99 +msgid ":guilabel:`Summary`: Enter a short description for the step." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:100 +msgid "" +":guilabel:`Assignment`: Using the drop-down menu, select the person assigned" +" to perform the activity. The default options are: :guilabel:`Ask at " +"launch`, :guilabel:`Default user`, :guilabel:`Coach`, :guilabel:`Manager`, " +"and :guilabel:`Employee`. If the **Fleet** app is installed, a " +":guilabel:`Fleet Manager` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:106 +msgid "" +"The selection for the :guilabel:`Assignment` role is in relation to the " +"employee. If :guilabel:`Coach` is selected, the employee's coach is assigned" +" to the activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:109 +msgid "" +"If :guilabel:`Default user` is selected, an :guilabel:`Assigned to` field " +"appears. Using the drop-down menu, select the user who will always be " +"assigned this activity." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:112 +msgid "" +":guilabel:`Interval`: Configure the fields in this line to determine the due" +" date of the activity. Enter a number in the first field, then, using the " +"drop-down menus in the following two fields, configure when the due date " +"should be created; (`#`) of :guilabel:`days`, :guilabel:`weeks`, or " +":guilabel:`months`, either :guilabel:`Before Plan Date` or :guilabel:`After " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:117 +msgid "" +"When the :guilabel:`Create Activities` for is completed, click " +":guilabel:`Save & Close` if there are no other steps to add, or click " +":guilabel:`Save & New` to add more steps, as needed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:121 +msgid "" +"A company specializing in after-school art programs has two separate " +"offboarding plans, one for the teachers working in the field, and one for " +"office workers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:124 +msgid "" +"The offboarding plan for the teachers is set for the :guilabel:`Art Program " +"Teachers` department, and includes specialized tasks relating to those jobs." +" These include ensuring all art supplies are catalogued and returned, all " +"student feedback forms are turned in, and all access badges and keys for the" +" various locations are returned." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:0 +msgid "An offboarding plan configured for art teachers." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:133 +msgid "Launch offboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:135 +msgid "" +"After an employee has given notice (typically two weeks) or once the company" +" has decided to terminate the working relationship with the employee, the " +"offboarding plan should be launched. Navigate to the " +":menuselection:`Employees app` and click on the departing employee profile. " +"Click the :guilabel:`Launch Plan` button, and a blank :guilabel:`Launch " +"Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The Launch Plan button on the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:143 +msgid "" +"Using the drop-down menu, select the desired offboarding plan in the " +":guilabel:`Plan` field. Then, using the calendar selector, set a date in the" +" :guilabel:`Plan Date` field. This is typically the day the employee gave " +"notice, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:147 +msgid "" +"The right-side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields for the various plan steps." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:150 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates. All scheduled activities " +"appear in the chatter of the employee profile." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:157 +msgid "Archive an employee" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:159 +msgid "" +"In Odoo, when an employee leaves the company they must be *archived*. This " +"step should be done *after* the employee has been fully offboarded. To " +"archive an employee, first navigate to the :menuselection:`Employees app`. " +"From here, locate the employee who is leaving the company, and click on " +"their employee card." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:164 +msgid "" +"The employee form loads, displaying all their information. Click the " +":icon:`fa-gear` :guilabel:`(gear)` icon in the top-left corner, and a drop-" +"down menu appears. Click :icon:`oi-archive` :guilabel:`Archive`, and an " +":guilabel:`Employee Termination` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:169 +#: ../../content/applications/hr/payroll/contracts.rst:281 +#: ../../content/applications/hr/time_off.rst:307 +msgid "Fill out the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:171 +msgid "" +":guilabel:`Departure Reason`: Select a reason the employee is leaving from " +"the drop-down menu. The default options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:174 +msgid "" +":guilabel:`Fired`: Select this option when an employee is being let go, and " +"the company has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:176 +msgid "" +":guilabel:`Resigned`: Select this option when the employee no longer wishes " +"to be employed, and the employee has given notice." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:178 +msgid "" +":guilabel:`Resigned: Retired`: Select this option when the employee is " +"retiring." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:179 +msgid "" +":guilabel:`Became Freelance`: Select this option when the employee is no " +"longer working for the company, but is becoming a freelance worker instead." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:181 +msgid "" +":guilabel:`Mutual Agreement`: Select this option when both parties have " +"agreed to terminate their working relationship." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:184 +msgid "" +":guilabel:`Contract End Date`: Using the calendar selector, select the last " +"day the employee is working for the company." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:186 +msgid "" +":guilabel:`Detailed Reason`: Enter a short description for the employee's " +"departure in this field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:187 +msgid "" +":guilabel:`Close Activities`: Tick the checkbox next to each type of " +"activity to close or delete any open activities associated with it. It is " +"recommended to tick **all** checkboxes that are applicable. The available " +"options are:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:191 +msgid "" +":guilabel:`Appraisals`: cancels all appraisals scheduled after the contract " +"end date." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:192 +msgid ":guilabel:`Contract`: applies an end date for the current contract." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:193 +msgid "" +":guilabel:`Company Car`: removes the employee as the driver for their " +"current company car, and :ref:`assigns the next driver " +"`, if applicable." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:195 +msgid "" +":guilabel:`Equipment`: unassigns the employee from any assigned equipment." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:197 +msgid "" +":guilabel:`HR Info`: Tick the checkbox next to :guilabel:`Send Access Link` " +"to send a download link to the employee's personal email address, containing" +" all their personal HR files." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:199 +msgid "" +":guilabel:`Private Email`: This field appears if the :guilabel:`HR Info` " +"checkbox is ticked. If there is a private email listed on the employee " +"profile, this field is automatically populated. If no private email address " +"is on their record, enter the private email address for the employee." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:203 +msgid "" +"When the form is complete, click :guilabel:`Apply`. The employee record is " +"archived, an email with a download link to their personal documents is sent " +"to the employee's private email address (if selected), and a red " +":guilabel:`Archived` banner appears in the top-right corner of the employee " +"form. The chatter logs the :guilabel:`Departure Date` and " +":guilabel:`Departure Reason`, and if an access link was emailed." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:-1 +msgid "The employee termination form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:213 +msgid "" +"While attempting to send the HR documents access link, an :guilabel:`Invalid" +" Operation` pop-up window may appear, displaying the following error " +"message:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:216 +msgid "" +":guilabel:`Employee's related user and private email must be set to use " +"\"Send Access Link\" function: (Employee Name)`" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:219 +msgid "" +"If this error appears, click :guilabel:`Close` to close the pop-up window, " +"then tick the :guilabel:`Send Access Link` checkbox to deselect it on the " +":guilabel:`Employee Termination` pop-up window." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:223 +msgid "" +"Click :guilabel:`Apply` to archive the employee and close the selected " +"activities on the :guilabel:`Employee Termination` pop-up window, returning " +"to the employee form." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:226 +msgid "Once the employee form, ensure the following fields are populated:" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:228 +msgid "" +":guilabel:`Private Information` tab: Ensure an email address is entered in " +"the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:230 +msgid "" +":guilabel:`HR Settings` tab: Ensure a :guilabel:`Related User` is selected " +"in the corresponding field." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:233 +msgid "" +"After the necessary information is entered, :ref:`resend the HR documents " +"access link `" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:239 +msgid "Send HR documents access link" +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:241 +msgid "" +"If the access link was not sent when first archiving the employee on the " +"*Employee Termination* form, it can be sent after the employee is archived " +"at any point." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:244 +msgid "" +"After an employee is archived, they are no longer visible on the main " +"**Employees** app dashboard. To view the archived employees, navigate to the" +" :menuselection:`Employees app` dashboard, and click the :icon:`fa-caret-" +"down` :guilabel:`(down arrow)` in the search bar to reveal a drop-down menu." +" Select :guilabel:`Archived`, towards the bottom of the :icon:`fa-filter` " +":guilabel:`Filters` column, then click away from the drop-down window to " +"close it." +msgstr "" + +#: ../../content/applications/hr/employees/offboarding.rst:250 +msgid "" +"Now, only archived employees appear on the dashboard. Click on the desired " +"employee to open their employee form. On this form, click the :icon:`fa-" +"gear` :guilabel:`(gear)` icon in the top-left corner, then click " +":guilabel:`Send HR Documents Access Link` from the resulting drop-down menu." +" The chatter logs that the link was sent." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:3 +#: ../../content/applications/hr/referrals.rst:28 +msgid "Onboarding" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:5 +msgid "" +"When a new employee is hired, it is important to have an onboarding " +"procedure that can be followed. This ensures that information, equipment, " +"and training are provided to the employee and any other necessary steps for " +"the business are assigned to the correct individuals." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:9 +msgid "" +"Proper onboarding ensures that new employees are given all the information " +"and tools needed to be successful in their roles and have a smooth " +"transition to their new job." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:13 +msgid "View onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:15 +msgid "" +"Before onboarding can begin, it is recommended to check the default " +"onboarding plan that comes preconfigured with the **Employees** app. To view" +" the current default plan, navigate to :menuselection:`Employees app --> " +"Configuration --> Activity Plan`. Click :guilabel:`Onboarding` to view the " +"detailed onboarding plan form." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:22 +msgid "The plan form displays the following information:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:24 +msgid ":guilabel:`Plan Name`: the specific name for the onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:25 +msgid "" +":guilabel:`Model`: specifies where this plan can be used. In this case, in " +"the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:26 +msgid "" +":guilabel:`Department`: if left blank (the default setting) this plan is " +"available for all departments. Limit the use of the plan to a specific " +"department by selecting the department using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:29 +msgid "" +":guilabel:`Activities To Create`: this tab lists all the onboarding steps. " +"Each row displays:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:31 +msgid "" +":guilabel:`Activity Type`: the specific activity for the step. The default " +"options are :guilabel:`Email`, :guilabel:`Call`, :guilabel:`Meeting`, " +":guilabel:`To-Do`, or :guilabel:`Upload Document`. If the **Sign** app is " +"installed, a :guilabel:`Request Signature` option is available." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:35 +msgid ":guilabel:`Summary`: a one line description of the step." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:36 +msgid "" +":guilabel:`Assignment`: chooses who completes the activity, relative to the " +"new hire:" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:38 +msgid "" +":guilabel:`Ask at launch`: choose the user in the :guilabel:`Assigned To` " +"field when :ref:`launching the onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:40 +msgid "" +":guilabel:`Default user`: choose a user who always handles this activity. " +"Defined in the :guilabel:`Assigned to` field." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:42 +msgid "" +":guilabel:`Manager`: assigns the employee's manager as defined on the " +"employee record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:43 +msgid "" +":guilabel:`Coach`: assigns the employee's coach as defined on the employee " +"record." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:44 +msgid ":guilabel:`Employee`: the new hire completes the activity." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:45 +msgid "" +":guilabel:`Fleet Manager`: assigns the designated **Fleet** app manager. " +"This option is only available if the **Fleet** app is installed." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:48 +msgid "" +":guilabel:`Assigned to`: this field remains blank, unless :guilabel:`Default" +" user` is selected for the :guilabel:`Assignment` field. If " +":guilabel:`Default user` is selected, this field is populated with the " +"selected user." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:51 +msgid "" +":guilabel:`Document to sign`: the corresponding document requiring a " +"signature." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:52 +msgid ":guilabel:`Interval`: the time when the activity is active." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:53 +msgid "" +":guilabel:`Unit`: the set time interval, either :guilabel:`days`, " +":guilabel:`weeks`, or :guilabel:`months`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:55 +msgid "" +":guilabel:`Trigger`: how scheduling is determined for the activity. Options " +"are either :guilabel:`Before Plan Date` or :guilabel:`After Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:59 +msgid "" +"A laptop must be set up and registered to a new employee the day before they" +" start work. The person who performs this step should always be the IT " +"Manager, Abby Jones." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:62 +msgid "" +"To configure this activity with these parameters, the :guilabel:`Activity " +"Type` is set to :guilabel:`To-Do`, with a summary of :guilabel:`Assign " +"Laptop`. The :guilabel:`Assignment` field is set to :guilabel:`Default " +"user`, and the :guilabel:`Assigned to` field is set to :guilabel:`Abby " +"Jones`. The :guilabel:`Interval` is :guilabel:`1`, and the :guilabel:`Unit` " +"is set to :guilabel:`days`. The :guilabel:`Trigger` is :guilabel:`Before " +"Plan Date`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "" +"An activity configured to assign a laoptop the day before an employee starts" +" work." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:72 +msgid "Onboarding plan steps" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:74 +msgid "" +"The default :guilabel:`Onboarding` plan includes three default steps. All " +"steps are :guilabel:`To-Do` activities, and are scheduled for the day the " +"onboarding plan is launched (:guilabel:`0 days Before Plan Date`)." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:78 +msgid "" +":guilabel:`Setup IT Materials`: the manager must gather and configure all IT" +" materials." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:79 +msgid "" +":guilabel:`Plan Training`: the manager must plan the training for the new " +"employee." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:80 +msgid "" +":guilabel:`Training`: the new employee must complete the training planned by" +" the manager." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "The three default steps in the Onboarding plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:88 +msgid "Modify onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:90 +msgid "" +"A single onboarding plan works only if the flow works for the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:93 +msgid "" +"If the onboarding plan is universal, add to or modify the default onboarding" +" plan. If department-specific onboarding plans are needed, :ref:`create a " +"new onboarding plan `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:97 +msgid "" +"To modify the default plan, first navigate to :menuselection:`Employees app " +"--> Configuration --> Activity Plan`, then click on :guilabel:`Onboarding`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:100 +msgid "" +"To modify a step, click on it. In the :guilabel:`Open: Activities` pop-up " +"window, make any desired modifications to the step, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:111 +msgid "Create onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:113 +msgid "" +"Some companies require different onboarding plans, when there are " +"department-specific onboarding procedures that do not apply to the whole " +"company. For these cases, a new department-specific onboarding plan must be " +"created." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:117 +msgid "" +"To create a new onboarding plan, :ref:`navigate to the desired plan and " +"configure all the desired steps `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:121 +msgid "" +"A company specializing in the manufacturing and selling of outdoor metal " +"furniture may have a large factory that produces the products, and a " +"separate sales office. This company may have two separate onboarding plans, " +"one for factory workers, and one for office workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:125 +msgid "" +"The onboarding plan for the factory workers is set for the " +":guilabel:`Manufacturing` department, and includes specialized tasks " +"relating to factory jobs. These include gathering the new employees uniform " +"and safety gear, assigning a safety course, emailing their team about the " +"new hire, going over benefits, and more." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:0 +msgid "An onboarding plan configured for factory workers." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:136 +msgid "Launch onboarding plan" +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:138 +msgid "" +"After an employee has been hired and their employee profile :ref:`is created" +" `, navigate to the desired employee's profile by " +"clicking on their Kanban card on the **Employees** app dashboard, then click" +" the :guilabel:`Launch Plan` button on their employee profile, and a blank " +":guilabel:`Launch Plan` pop-up window loads." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:143 +msgid "" +"In the :guilabel:`Plan` field, choose the desired onboarding plan. Then, " +"using the calendar selector, set a date in the :guilabel:`Plan Date` field. " +"This is typically the employee's first day, but any date can be selected." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:147 +msgid "" +"The right side of the :guilabel:`Launch Plan` pop-up window displays all the" +" steps in the selected plan, grouped by what was selected in the " +":guilabel:`Assignment` fields on the :ref:`plan form `." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:151 +msgid "" +"Once the :guilabel:`Plan` and :guilabel:`Plan Date` fields are configured, " +"click the :guilabel:`Schedule` button, and Odoo schedules everything in the " +"plan, according to their respective due dates." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:155 +msgid "" +"All scheduled activities appear in the both chatter of the employee profile," +" and in the chatter of the user's with assignments relating to the plan." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:159 +msgid "" +"If any activity assignments were configured to :guilabel:`Ask at launch`, an" +" :guilabel:`Assigned to` field appears on the :guilabel:`Launch Plan` pop-up" +" window. Using the drop-down menu, select the user responsible for all the " +"unassigned activities." +msgstr "" + +#: ../../content/applications/hr/employees/onboarding.rst:-1 +msgid "All onboarding tasks scheduled in the chatter." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:3 +msgid "Employee retention report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:5 +msgid "" +"It is possible to determine the retention rate for a company by modifying an" +" existing report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:7 +msgid "" +"First, navigate to :menuselection:`Employees app --> Reporting --> " +"Contracts` to open the :guilabel:`Employee Analysis` report. This report " +"shows the number of all employees for the :guilabel:`Last 365 Days`, in a " +"default :icon:`fa-line-chart` :guilabel:`Line Chart`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "The default Employees Analysis report." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:15 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# Departure " +"Employee` in the list, then click away from the drop-down menu to close it. " +"Now, the report shows all the employees who were archived for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:20 +msgid "" +"To view this information in an easier format, click the :icon:`oi-view-" +"pivot` :guilabel:`(Pivot)` icon in the upper-right corner, and the data is " +"presented in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:23 +msgid "" +"The various employees, organized by department, populate the rows. The " +"columns display the following totals: the monthly :guilabel:`Wage`, the " +":guilabel:`Fuel Card` budget, total :guilabel:`Annual Employee Budget` (also" +" referred to as the *annual salary*), the number of :guilabel:`New " +"Employees`, as well as the number of :guilabel:`Departure Employees` " +"(employees who left)." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:-1 +msgid "" +"The Employees Analysis report, modified to show departed employees only." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:33 +msgid "Employee retention rate comparison report" +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:35 +msgid "" +"It is possible to compare data only for employees who left, compared to the " +"total current employees, between two separate time periods. This is commonly" +" referred to as the *employee retention rate*." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:38 +msgid "" +"To view these metrics, first open the :guilabel:`Employee Analysis` report " +"by navigating to :menuselection:`Employees app --> Reporting --> Contracts`." +" Click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the upper-right" +" corner to view the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:42 +msgid "" +"Next, click the :guilabel:`Measures` :icon:`fa-caret-down` button in the " +"upper-left corner, revealing a drop-down menu. Click :guilabel:`# New " +"Employees`, :guilabel:`Annual Employee Budget`, :guilabel:`Fuel Card`, and " +":guilabel:`Wage` in the list, to deselect these metrics and hide them in the" +" table. Then, click :guilabel:`Count` at the bottom of the list to enable " +"that metric." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:47 +msgid "" +"Click away from the drop-down menu to close it. Now, the report shows all " +"the employees who left the company (:guilabel:`# Departure Employee`), as " +"well as the total number of employees (:guilabel:`Count`), for the " +":guilabel:`Last 365 Days`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:51 +msgid "" +"To compare the data for the current year with the previous year, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar, revealing " +"multiple filter and grouping options. Click :guilabel:`Last 365 Days` in the" +" :icon:`fa-filter` :guilabel:`Filters` column, to turn off that filter. " +"Then, click :guilabel:`Date`, and click the current year (in this example, " +":guilabel:`2024`) from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:57 +msgid "" +"Once a selection is made beneath :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Date: Previous Year` in the new column, " +"then click off of the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:62 +msgid "" +"In Odoo, in order to access the :icon:`fa-adjust` :guilabel:`Comparison` " +"column, a specific time *other than* :guilabel:`Last 365 Days` **must** be " +"selected. If not, the :icon:`fa-adjust` :guilabel:`Comparison` column is " +"**not** visible." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:66 +msgid "" +"Now, the pivot table displays the total number of employees who left the " +"company (:guilabel:`# Departure Employee`), as well as the total number of " +"employees (:guilabel:`Count`) in the columns. These are further divided by " +"the two different years, and also displays the :guilabel:`Variation` between" +" the two." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:71 +msgid "" +"The rows display the departments, and lists each individual employee for " +"each department, in the rows." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:74 +msgid "" +"For a more concise view of this report, click :icon:`fa-minus-square-o` " +":guilabel:`Total` above the top row of the departments and employees, to " +"collapse the rows. Now, the table presents the total number of employees who" +" left the company for both years, compared to the total number of employees " +"for both years, including the difference, in a percentage." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:80 +msgid "" +"In this example, :guilabel:`3` employees out of :guilabel:`83` left in 2023," +" and :guilabel:`8` employees out of :guilabel:`202` left in 2024. There was " +"a :guilabel:`166.67%` increase in the employees who left in 2024 as compared" +" to 2023. Additionally, there was a :guilabel:`143.37%` increase in the " +"total number of employees in 2024 as compared to 2023." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "" +"The report modified to show the difference between two years of employees " +"who left." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:89 +msgid "" +"To view more detailed rates for each department, click :icon:`fa-plus-" +"square` :guilabel:`Total` in the single row, revealing a drop-down menu, and" +" click :guilabel:`Department`. Click away from the drop-down to close it, " +"and now the pivot table displays the total number of employees who left " +"(:guilabel:`# Departure Employee`), the total number of employees " +"(:guilabel:`Count`), and the :guilabel:`Variation` (in a percentage) for " +"both 2023 and 2024, organized by department." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:96 +msgid "" +"In this example, it can be determined that the :guilabel:`Management` " +"department had the best retention rate in 2024 as compared to 2023, with a " +":guilabel:`Variation` rate of :guilabel:`-100%`. Additionally, it can be " +"determined that the :guilabel:`Management / Research & Development` " +"department had the most turnover, with a :guilabel:`Variation` of " +":guilabel:`300%`." +msgstr "" + +#: ../../content/applications/hr/employees/retention_report.rst:0 +msgid "The expanded employee retention report by department." +msgstr "" + +#: ../../content/applications/hr/fleet.rst:5 +msgid "Fleet" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:3 +msgid "Accidents" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:5 +msgid "" +"When managing a fleet, accidents are inevitable. Tracking accidents is " +"crucial for understanding vehicle maintenance costs and identifying safe " +"drivers." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:8 +msgid "" +"Odoo's **Fleet** app offers multiple ways of tracking accidents. Below are " +"step-by-step instructions for one possible method to monitor accidents and " +"repair costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:12 +msgid "Structure" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:14 +msgid "" +"For this use case, go to :menuselection:`Fleet app --> Fleet --> Services`. " +"On the :ref:`service form `, two :ref:`service types " +"` are created: `Accident - Driver's Fault` and `Accident - " +"No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:18 +msgid "" +"This setup records repairs associated with accidents and organizes them by " +"fault." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:20 +msgid "" +"When an accident occurs, a service record is created. The specific repairs " +"needed for the accident are logged in the *Description* of the service " +"record, and the details about the accident are logged in the *Notes* " +"section." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:24 +msgid "" +"With this organizational structure, it is possible to view all accidents " +"organized by fault, car, driver, or cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:28 +msgid "To manage accidents, the creation of service records is **required**." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:30 +msgid "" +"Refer to the :doc:`service` documentation for detailed instructions on " +"creating service records in Odoo's **Fleet** app." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:34 +msgid "Log accidents and repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:36 +msgid "" +"To log an accident and initiate the repair process, the first step is to " +":ref:`create a service record ` detailing the specific " +"repairs needed." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:40 +msgid "" +"Some accidents require multiple repairs with several different vendors. For " +"these scenarios, a separate service record is needed for each vendor " +"performing repairs. To keep records organized, it is recommended to keep the" +" *Notes* field identical, and attach the same important documentation, such " +"as a police report." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:45 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +"main :guilabel:`Services` dashboard. Click :guilabel:`New` in the top-left " +"corner, and a blank service form loads." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:50 +msgid "" +":guilabel:`Description`: enter the description of repairs needed to fully " +"repair the vehicle, such as `Bodywork`, `Windshield Replacement`, or " +"`Replacement Bumper, Tires, and Windows`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:52 +msgid "" +":guilabel:`Service Type`: for this example, select either `Accident - " +"Driver's Fault` or `Accident - No Fault`, depending on the situation." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:55 +msgid "" +"When entering either of these two :guilabel:`Service Types` for the first " +"time, type in the new service type, then click :guilabel:`Create (new " +"service type)`. A :guilabel:`Create Service Type` pop-up window appears, " +"with the new service type populating the :guilabel:`Name` field. In the " +":guilabel:`Category` field, select :guilabel:`Service` from the drop-down " +"menu, then click the :guilabel:`Save & Close` button." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:61 +msgid "" +"Once an accident service type has been added to the database, it is " +"available to select from the drop-down menu in the :guilabel:`Service Type` " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:63 +msgid "" +":guilabel:`Date`: using the calendar popover window, select the date the " +"accident occurred. Navigate to the desired month using the :icon:`fa-" +"chevron-left` :icon:`fa-chevron-right` :guilabel:`(arrow)` icons, then click" +" the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:66 +msgid "" +":guilabel:`Cost`: leave this field blank, as the repair cost is not yet " +"known." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:67 +msgid "" +":guilabel:`Vendor`: select the vendor performing the repairs using 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 and edit...` to :ref:`add and configure the vendor " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:71 +msgid "" +":guilabel:`Vehicle`: select the vehicle that was in the accident from the " +"drop-down menu. When the vehicle is selected, the :guilabel:`Driver` field " +"is populated, and the unit of measure for the :guilabel:`Odometer Value` " +"field appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:74 +msgid "" +":guilabel:`Driver`: the current driver listed for the selected vehicle " +"populates this field when the :guilabel:`Vehicle` is selected. If a " +"different driver was operating the vehicle when the accident occurred, " +"select the correct driver from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:77 +msgid "" +":guilabel:`Odometer Value`: enter the odometer reading when the accident " +"occurred. The units of measure are either in kilometers (:guilabel:`km`) or " +"miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:80 +msgid "" +":guilabel:`NOTES`: enter the specific details of the accident at the bottom " +"of the service form, such as `Hit a deer` or `Rear-ended at an intersection " +"while stopped`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:83 +msgid "" +"Odoo provides the ability to attach any important paperwork, such as repair " +"estimates and police reports, to the service record. To do so, click the " +":icon:`fa-paperclip` :guilabel:`(paperclip)` icon, located in the *chatter* " +"of the form, and a file explorer pop-up window appears. Navigate to the " +"desired record, and click :guilabel:`Open` to upload the file." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:89 +msgid "" +"Once a file is added to a service record, a :guilabel:`Files` section " +"appears in the *chatter*. To attach more records, click :icon:`fa-plus-" +"square` :guilabel:`Attach files` to add more documents." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "Enter the information for an accident repair." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:97 +msgid "Service stages" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:99 +msgid "In Odoo's **Fleet** app, there are four default service stages:" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:103 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:18 +msgid "New" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:105 +msgid "" +"The default stage when a service record is created. The service has been " +"requested, but repairs have not begun. The :guilabel:`Cost` field for this " +"stage remains zero." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:108 +msgid "Running" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:110 +msgid "" +"The repair is in-process, but not yet complete. The estimate for repairs is " +"listed in the :guilabel:`Cost` field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:113 +msgid "Completed" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:115 +msgid "" +"All repairs listed on the service form have been completed. The " +":guilabel:`Cost` field is updated to reflect the final total cost charged " +"for the repairs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:118 +msgid "Cancelled" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:120 +msgid "The service request has been cancelled." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:122 +msgid "" +"During the repair process, change the service status to reflect the " +"vehicle's current state in one of two ways: on the individual :ref:`service " +"record `, or in the :ref:`Kanban service view " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:129 +msgid "Service record" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:131 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. Next, click on the individual service record to" +" open the detailed service form. Click the desired stage in the top-right " +"corner, above the service form, to change the status." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The stages as seen from the service form." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:143 +msgid "" +"Open the main *Services* dashboard, by navigating to :menuselection:`Fleet " +"app --> Fleet --> Services`. First, click the :icon:`oi-view-kanban` " +":guilabel:`Kanban` icon in the top-right of the screen, which organizes all " +"repairs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:147 +msgid "" +"Next, remove the default :guilabel:`Service Type` filter in the search bar. " +"Upon doing so, all services appear in a Kanban view, organized by their " +"respective :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:150 +msgid "Drag-and-drop the service record to the desired stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Kanban view of stages, with a card being dragged and dropped to the " +"Running stage." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:156 +msgid "Accident reporting" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:158 +msgid "" +"One of the main reasons to track accidents using the method outlined in this" +" document is the ability to view the total accident cost, determine the " +"safest drivers, and calculate the actual total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:162 +msgid "" +"The main :ref:`Services dashboard ` displays all " +"the various accident information, while the :ref:`Reporting dashboard " +"` displays the total cost for specific vehicles." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:169 +msgid "Services dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:171 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services` to view the " +":guilabel:`Services` dashboard. All service records are displayed in a " +":icon:`oi-view-list` :guilabel:`(List)` view, grouped alphabetically, by " +":guilabel:`Service Type`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:175 +msgid "" +"The two service types created for accident tracking appear in the list: " +":guilabel:`Accident - Driver Fault` and :guilabel:`Accident - No Fault`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:178 +msgid "" +"Each grouping displays the number of records within each type, and lists the" +" individual records beneath each grouping title." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:182 +msgid "" +"In this example, there are three accidents where the driver was at fault, " +"and one accident that was not the driver's fault. This dashboard also " +"displays the estimated total :guilabel:`Cost` for all the accidents in each " +"group." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:186 +msgid "" +"An estimated `$3,284.00` dollars are costs from driver-caused accident " +"repairs. The no-fault accident has no cost associated with it, since the " +"repair has not been completed, and no estimate exists yet." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:0 +msgid "Accident services, with the total costs highlighted." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:194 +msgid "" +"The total :guilabel:`Cost` calculates **all** costs on the repair form, " +"including estimated costs, as well as final repair costs. This number may " +"not be accurate, if there are any repairs in the *Running* stage, and the " +"final bill has not yet been calculated." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:201 +msgid "Reporting dashboard" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:203 +msgid "" +"Navigate to :menuselection:`Fleet app --> Reporting --> Costs` to view the " +":menuselection:`Cost Analysis` report. This report displays a :icon:`fa-" +"bar-chart` :guilabel:`(Bar Chart)` of all :guilabel:`Contract` and " +":guilabel:`Service` costs for the current year, organized by month " +"(:guilabel:`Date : (year)`), by default. The :guilabel:`Sum`, represented by" +" a gray dotted line, is the combined total of both the :guilabel:`Contract` " +"and :guilabel:`Service` costs." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:209 +msgid "" +"To view the total cost by vehicle, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Bar)` icon at the right of the search bar, " +"revealing a drop-down menu. Click :guilabel:`Vehicle` in the :icon:`oi-" +"group` :guilabel:`Group By` column, and the data is organized by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:213 +msgid "" +"This displays the true cost for each vehicle, including both the contract " +"cost (such as the monthly vehicle lease cost) and all service costs, " +"including all accidents. Hover over a column to reveal a data popover " +"window, which displays the vehicle name and the total cost. This allows for " +"a more complete view of the vehicle cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "The Cost Analysis report, displaying total costs by vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:221 +msgid "" +"To view the individual cost details for both contract costs and repairs, " +"click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right " +"corner of the :guilabel:`Cost Analysis` dashboard. This displays each " +"vehicle on a separate line, and displays the :guilabel:`Contract` cost and " +":guilabel:`Service` cost, as well as the :guilabel:`Total` cost." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The Cost Analysis report, displaying the contract and service costs separately, as well as\n" +"the total." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:231 +msgid "" +"The :icon:`oi-view-pivot` :guilabel:`(Pivot)` view organizes the data by " +"vehicle, by default, therefore grouping the data by :guilabel:`Vehicle` is " +"not required. If this filer is already activated, it does not affect the " +"presented data." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:236 +msgid "Manage accident repairs" +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:238 +msgid "" +"For companies with multiple employees, who manage a large fleet of vehicles," +" displaying only service records in the :guilabel:`New` and " +":guilabel:`Running` stages can be time-saving, if there are a large number " +"of records in the *Services* dashboard." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:242 +msgid "" +"Navigate to :menuselection:`Fleet app --> Fleet --> Services`, where all " +"service requests are organized by :guilabel:`Service Type`. Next, click the " +":icon:`fa-caret-down` :guilabel:`(Toggle Search Panel)` icon at the right of" +" the search bar, revealing a drop-down menu. Click :guilabel:`Add Custom " +"Filter` in the :icon:`fa-filter` :guilabel:`Filters` column, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:248 +msgid "Three drop-down fields need to be configured on the pop-up window." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:250 +msgid "In the first field, scroll down, and select :guilabel:`Stage`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:252 +msgid "Leave the second field set to :guilabel:`=`." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:254 +msgid "Select :guilabel:`Running` from the drop-down menu in the last field." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:256 +msgid "" +"Next, click the :icon:`fa-plus` :guilabel:`(plus)` icon to the right of the " +"last field, and an identical rule appears beneath the current rule." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:259 +msgid "" +"Then, change :guilabel:`Running` to :guilabel:`New` in the third field of " +"the second rule, leaving the other fields as-is." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:262 +msgid "" +"Click the :guilabel:`Add` button at the bottom to add the new custom filter." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:-1 +msgid "" +"The filter settings to be added to only display new and running services." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:267 +msgid "" +"This slight modification only presents services in the :guilabel:`New` and " +":guilabel:`Running` stages. This is a helpful report for a company managing " +"a high number of repairs at any given time." +msgstr "" + +#: ../../content/applications/hr/fleet/accidents.rst:270 +msgid "" +"To have this report appear as the default report when opening the " +":guilabel:`Services` dashboard, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` icon at the far-right of the search bar. " +"Next, click :guilabel:`Save current search`, beneath the :icon:`fa-star` " +":guilabel:`Favorites` column, which reveals another drop-down column beneath" +" it. Tick the checkbox beside :guilabel:`Default Filter`, then click " +":guilabel:`Save`. Then, this customized :guilabel:`Services` dashboard " +"appears, by default, any time the :guilabel:`Services` dashboard is " +"accessed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:3 +msgid "Models & manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:5 +msgid "" +"Odoo's **Fleet** app categorizes each vehicle by *manufacturer* and *model* " +"(e.g. `BMW`, `X2`). Before the vehicle can be added to the Odoo database, " +"its :ref:`manufacturer ` and a :ref:`model ` records must already exist in the database." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:12 +msgid "Manufacturers" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:14 +msgid "" +"Odoo's **Fleet** app comes preconfigured 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/fleet/models.rst:18 +msgid "" +"The default filter, :guilabel:`With Models`, displays only manufacturers " +"that already have vehicle models. Remove the default filter to view *all* " +"manufacturers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:21 +msgid "" +"Manufacturers re listed alphabetically, and each card shows how many " +"specific :ref:`models ` are configured for each particular " +"manufacturer." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Manufacturer card with the amount of models listed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:30 +msgid "Add a manufacturer" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:32 +msgid "" +"To add a new manufacturer to the database, click :guilabel:`New` in the " +"upper-left corner, to open a blank manufacturers form. Type the name of the " +"manufacturer in the :guilabel:`Name` field, and select an image to upload " +"for the logo." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:39 +msgid "Models" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:41 +msgid "" +"When adding a vehicle to the fleet, specify the vehicle model to maintain " +"updated records, which keeps track of specific details, like maintenance " +"schedules and parts compatibility." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:44 +msgid "" +"Unlike :ref:`manufacturers `, models do **not** come " +"preconfigured in the **Fleet** app. When a new vehicle model joins the " +"fleet, the model (and, if necessary, the manufacturer) **must** be " +":ref:`added to the database `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:51 +msgid "Add a model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:53 +msgid "" +"To add a new vehicle model, navigate to :menuselection:`Fleet app --> " +"Configuration --> Models`. Click :guilabel:`New` in the upper-left corner, " +"and enter the following information on the new model form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:58 +msgid "" +"Depending on the installed :doc:`localization " +"<../../finance/fiscal_localizations>`, some fields or sections may not " +"appear." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:61 +msgid ":guilabel:`Model name`: Enter the model name in the field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:62 +msgid "" +":guilabel:`Manufacturer`: Using the drop-down menu, select the manufacturer." +" If it is not configured, :ref:`add the manufacturer `" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:64 +msgid "" +":guilabel:`Vehicle Type`: Using the drop-down menu, select one of two " +"preconfigured vehicle types, either :guilabel:`Car` or :guilabel:`Bike`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:68 +msgid "" +"Additional vehicle types can **not** be added. **Fleet** keeps them fixed to" +" preserve its **Payroll** integration, where vehicles may count as employee " +"benefits." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:71 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select a :ref:`category " +"` for the vehicle or :ref:`create a new one `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:75 +msgid "Information tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:77 +msgid "" +"In the :guilabel:`Information` tab, specify details about the car model, " +"such as the car size, passenger capacity, cost settings (applicable to the " +"Belgium localization only), and engine information." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:82 +msgid "Model" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:84 +msgid "" +":guilabel:`Seats Number`: Enter how many passengers the vehicle can " +"accommodate." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:85 +msgid ":guilabel:`Doors Number`: Enter the number of doors the vehicle has." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:86 +msgid ":guilabel:`Model Year`: Enter the year the vehicle was manufactured." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:87 +msgid "" +":guilabel:`Trailer Hitch`: Tick this checkbox if the vehicle has a trailer " +"hitch installed." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:90 +#: ../../content/applications/hr/payroll.rst:358 +msgid "Salary" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:92 +msgid "" +"The :guilabel:`Salary` section **only** appears 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/models.rst:96 +msgid "" +":guilabel:`Can be requested`: Tick this checkbox if employees can request " +"this model vehicle, if a vehicle is part of their employee contract." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:98 +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/models.rst:100 +msgid "" +":guilabel:`C02 fee`: Represents the carbon dioxide emission fee paid to the " +"Belgian government. This value is automatically calculated, based on Belgian" +" laws and regulations, and **cannot** be modified. The value is based on the" +" figure entered in the :guilabel:`CO2 Emissions` field (in the " +":guilabel:`Engine` section of the :guilabel:`Information` tab) on the " +"vehicle form." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:106 +msgid "" +"Modifying the :guilabel:`CO2 Emissions` field adjusts the value in the " +":guilabel:`CO2 fee` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:108 +msgid "" +":guilabel:`Cost (Depreciated)`: Enter the monthly vehicle cost, which " +"appears in the salary configurator for future employees. This value impacts " +"the gross and net salary of the employee 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." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:113 +msgid "" +":guilabel:`Total Cost (Depreciated)`: This value is the combination of the " +":guilabel:`Cost (Depreciated)` and the :guilabel:`C02 fee` fields. It also " +"depreciated over time." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:117 +msgid "Engine" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:119 +msgid "" +":guilabel:`Fuel Type`: Using the drop-down menu, select the type of fuel the" +" vehicle uses. The default options are :guilabel:`Diesel`, " +":guilabel:`Gasoline`, :guilabel:`Full Hybrid` :guilabel:`Plug-in Hybrid " +"Diesel`, :guilabel:`Plug-in Hybrid Gasoline`, :guilabel:`CNG`, " +":guilabel:`LPG`, :guilabel:`Hydrogen`, or :guilabel:`Electric`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:123 +msgid "" +":guilabel:`Range`: Enter the distance the vehicle can travel on one tank of " +"gas, or one battery charge, in kilometers." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:125 +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/models.rst:127 +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/models.rst:129 +msgid "" +":guilabel:`Transmission`: Using the drop-down menu, select the type of " +"transmission, either :guilabel:`Manual` or :guilabel:`Automatic`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:131 +msgid "" +":guilabel:`Power Unit`: Using the drop-down menu, select how the vehicle's " +"power is measured, either in kilowatts or horsepower." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:133 +msgid "" +":guilabel:`Power`: If the vehicle is electric or hybrid, enter the power the" +" vehicle uses in kilowatts (:guilabel:`kW`). This field only appears if " +":guilabel:`kW` is selected for the :guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:136 +msgid "" +":guilabel:`Horsepower`: Enter the vehicle's horsepower in this field. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:138 +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. This " +"field only appears if :guilabel:`Horsepower` is selected for the " +":guilabel:`Power` field." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:143 +msgid "" +":guilabel:`Horsepower Taxation`: Enter the amount of taxes incurred " +"according to the engine specifications. The number is dependent on the local" +" tax laws, therefore it is recommended to check with the accounting " +"department to ensure the correct taxation amount is entered. This field only" +" appears if the :guilabel:`Power` field is set to :guilabel:`Horsepower`." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:147 +msgid "" +":guilabel:`Tax Deduction`: The percentage that can be deducted from taxes is" +" populated based on the localization, and **cannot** be modified. This field" +" only appears for certain localizations." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:151 +msgid "Vendors tab" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:153 +msgid "" +"Specify the vendors a vehicle can be purchased from in this tab. With proper" +" setup, :doc:`requests for quotations " +"<../../inventory_and_mrp/purchase/manage_deals/rfq>` for vehicles can be " +"created through Odoo's **Purchase** app." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:157 +msgid "" +"To add a vendor, click :guilabel:`Add` in the upper-left corner of the " +":guilabel:`Vendors` tab. This opens an :guilabel:`Add: Vendors` pop-up " +"window, with a list of all the vendors currently in the database. Add a " +"vendor by ticking the checkbox next to the vendor name, then click " +":guilabel:`Select`. No limitations exist on the number of vendors that can " +"be added to this list." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:162 +msgid "" +"If a vendor is *not* already in the database, add a vendor by clicking " +":guilabel:`New` in the bottom-left of the :guilabel:`Add: Vendors` pop-up " +"window. In the :guilabel:`Create Vendors` form that appears, enter the " +"necessary information, then click :guilabel:`Save & Close` to add the " +"vendor, or click :guilabel:`Save & New` to add the current vendor and create" +" another new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:-1 +msgid "Vendor form to fill out when adding a new vendor." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:173 +msgid "Model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:175 +msgid "" +"To aid with fleet organization, it is recommended to have vehicle models " +"housed under a specific category. Model categories are set on the " +":ref:`vehicle model form `." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:178 +msgid "" +"Odoo does **not** come with any categories preconfigured; all categories " +"**must** be added." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:180 +msgid "" +"To view any categories currently set up in the database, navigate to " +":menuselection:`Fleet app --> Configuration --> Categories`. All categories " +"are displayed in a list view." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:186 +msgid "Add a new model category" +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:188 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner of the :guilabel:`Categories` dashboard. A new entry line appears at " +"the bottom of the list. Type in the new category, then either click " +":guilabel:`Save`, or click anywhere on the screen, to save the entry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:193 +msgid "" +"To reorganize how the categories appear in the list, click on the :icon:`oi-" +"draggable` :guilabel:`(draggable)` icon to the left of any desired category " +"name, and drag the line to the desired position." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:197 +msgid "" +"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 number of passengers the vehicle can carry." +msgstr "" + +#: ../../content/applications/hr/fleet/models.rst:202 +msgid "" +"When used with the **Inventory** app, the :guilabel:`Max Weight` and " +":guilabel:`Max Volume` fields track a vehicle's capacity. This helps manage " +"in-house deliveries by :doc:`showing how much space and weight remain for " +"loading products " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:3 +msgid "Adding 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 records." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:8 +msgid "" +"Upon opening the :menuselection:`Fleet` application, all vehicles are " +"organized within the :guilabel:`Vehicles` dashboard, which is the default " +"dashboard. Each vehicle is displayed in its corresponding Kanban stage, " +"based on its status. The default stages are :guilabel:`New Request`, " +":guilabel:`To Order`, :guilabel:`Registered`, and :guilabel:`Downgraded`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:18 +msgid "" +"Before registering any vehicles, review two **Fleet** settings that directly" +" affect day-to-day operations and employee benefits:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:21 +msgid "" +":ref:`End Date Contract Alert ` — emails the contract's " +"*Responsible* person a set number of days before the vehicle agreement " +"expires, so renewals or returns aren't missed." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:23 +msgid "" +":ref:`New Vehicle Request ` — (Belgian Payroll localization " +"only) blocks employees from requesting a new company car through the salary " +"configurator, once the available vehicles already exceeds the defined limit," +" helping control benefits costs." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:27 +msgid "" +"To access the settings menu, go to :menuselection:`Fleet app --> " +"Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:32 +msgid "End Date Contract Alert" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:34 +msgid "" +"The :guilabel:`End Date Contract Alert` field shows how many days before the" +" end of a vehicle contract an alert should be sent. The :ref:`responsible " +"parties ` receive an email informing them that a vehicle " +"contract is about to expire in the number of days defined in this field." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +msgid "Settings available for the Fleet application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:45 +msgid "Responsible parties" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:47 +msgid "" +"To determine 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 receives the alert." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:51 +msgid "" +"To open a contract from a list of all contracts, navigate to " +":menuselection:`Fleet app --> Fleet --> Contracts` and all contracts appear " +"in the list. Click on a :guilabel:`Contract` to open it. In the " +":guilabel:`Information` section of the contract, look under " +":guilabel:`Responsible` to see who receives expiration alerts." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:56 +msgid "" +"An individual contract can also be opened from a specific vehicle 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. Only contracts associated with the " +"vehicle appear in the list. Click on an individual contract to open it. The " +":guilabel:`Responsible` person is listed on the contract." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:65 +msgid "New Vehicle Request (Belgian Payroll - Fleet)" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:67 +msgid "" +"Enter the maximum fleet size that may be reached through the salary-" +"configurator flow. When the total number of available vehicles (vehicles " +"without an assigned driver) is equal to or below this limit, employees can " +"request a new company car. Once the available vehicles exceeds the limit, " +"the request option is hidden." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:73 +msgid "" +"If the :guilabel:`New Vehicle Request` limit is set to 20 vehicles, and " +"there are 25 vehicles available, employees cannot request a new car and must" +" select from the 25 already available. If there are only 10 cars available, " +"then the employee would be able to request a new vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:78 +msgid "" +"This settings option **only** appears if the :guilabel:`Belgian-Payroll-" +"Fleet` module is installed for the Belgian localization." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:82 +msgid "Add a vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:84 +msgid "" +"To add a new vehicle to the fleet from the :guilabel:`Vehicles` dashboard, " +"click the :guilabel:`New` button in the top-left corner, and a blank vehicle" +" form loads. Then, proceed to enter the vehicle information on the vehicle " +"form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:91 +msgid "Vehicle form fields" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:93 +msgid "" +":guilabel:`Model`: Using the drop-down menu, select the vehicle's model. " +"Once a model is selected, additional fields may appear on the form. If the " +"model is not listed, type in the model name, and click either " +":guilabel:`Create \"model\"`, or :guilabel:`Create and edit...` to " +":ref:`create a new model and edit the model details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:97 +msgid ":guilabel:`License Plate`: Enter the vehicle's license plate number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:98 +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:-1 +msgid "The new vehicle form, showing the model section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:105 +msgid "" +"The :guilabel:`Model` is the *only* required field on the new vehicle form. " +"When a model is selected, other fields appear on the vehicle form, and " +"relevant information auto-populates the 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:113 +msgid "Driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:115 +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:118 +msgid "" +":guilabel:`Driver`: Using the drop-down menu, select the driver for the " +"vehicle. If the driver is not listed, :ref:`create the new driver, and edit " +"the driver details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:123 +msgid "" +"A driver does *not* have to be an employee. When creating a new driver, the " +"driver is added to the **Fleet** app, *not* the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:126 +msgid "" +"If the **Contacts** app is installed, the driver information is also stored " +"there." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:128 +msgid "" +":guilabel:`Mobility Card`: If the selected driver has a mobility card (such " +"as a gas card) listed on their employee record in the **Employees** " +"application, the mobility card number automatically appears in this field. " +"If there is no mobility card listed, and one should be added, :ref:`edit the" +" employee record ` in the **Employees** application." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:132 +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 \"future driver\"` or :guilabel:`Create " +"and edit...` to :ref:`create a new future driver, and edit the driver " +"details `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:138 +msgid "" +"If this field is populated, a :guilabel:`Apply New Driver` button appears on" +" the vehicle form. Click the :guilabel:`Apply New Driver` button to change " +"the driver information." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:141 +msgid "" +":guilabel:`Plan To Change Car`: Tick this box when the current driver " +"already knows they'll switch to another vehicle, whether they are awaiting " +"an ordered car, using this one only temporarily, or are leaving the company." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:144 +msgid "" +":guilabel:`Assignment Date`: Using the calendar selector, select when the " +"vehicle is available for another driver. If this field is left blank, that " +"indicates the vehicle is currently available, and can be assigned to another" +" driver. If it is populated, the vehicle is not available for another driver" +" until the selected date." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:148 +msgid "" +":guilabel:`Company`: Select the company from the drop-down menu. This field " +"only appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:154 +msgid "Create a new driver" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:156 +msgid "" +"If a driver is not already in the system, the new driver should first be " +"configured and added to the database. A new driver can be added either from " +"the :guilabel:`Driver` or :guilabel:`Future Driver` fields on the " +":ref:`vehicle form `." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:160 +msgid "" +"First, type in the name of the new driver in either the :guilabel:`Driver` " +"or :guilabel:`Future Driver` field, then click :guilabel:`Create and " +"edit...`. A :guilabel:`Create Driver` or :guilabel:`Create Future Driver` " +"form appears, depending on which field initiated the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:164 +msgid "" +"Both the :guilabel:`Create Driver` and :guilabel:`Create Future Driver` " +"forms are identical, and are stored in the **Contacts** app. :doc:`Configure" +" the new contact <../../essentials/contacts>`, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:169 +msgid "" +"Depending on the installed applications, different tabs or fields may be " +"visible on the :guilabel:`Create Driver` and :guilabel:`Create Future " +"Driver` forms." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:175 +msgid "Vehicle" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:177 +msgid "" +"This section captures key physical details of a vehicle. Selecting an " +"existing Model may auto-fill some fields." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:180 +msgid "Fill in the following fields on the form:" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:182 +msgid "" +":guilabel:`Category`: Using the drop-down menu, select the vehicle category " +"from the available options. If the **Inventory** app is installed, the " +"category affects any configured :doc:`dispatch management system " +"<../../inventory_and_mrp/inventory/shipping_receiving/setup_configuration/dispatch>`." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:186 +msgid "" +":guilabel:`Order Date`: Using the calendar selector, select the date the " +"vehicle was ordered. Keeping track of how long vehicles have been in the " +"fleet can help when making decisions on expensive repairs, or help decide " +"when to surrender a vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:189 +msgid "" +":guilabel:`Registration Date`: Using the calendar selector, select the date " +"the vehicle was registered. Many regions require proper registration, so " +"keeping track of registration dates is important." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:192 +msgid "" +":guilabel:`Cancellation Date`: Using the calendar selector, select the date " +"the vehicle lease expires, or when the vehicle is no longer part of the " +"fleet (e.g., sold, plates surrendered)." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:194 +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. Every vehicle has a unique number, so in the event of a theft or " +"accident, a vehicle can be identified with this unique number." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:197 +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)`. Keeping track of a vehicle's mileage is crucial when " +"determining the value of the vehicle for both tax purposes and resale value." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:201 +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:203 +msgid "" +":guilabel:`Location`: Type in the specific location where the vehicle is " +"typically located in this field. The entry should clearly explain where the " +"vehicle can be found, such as `Main Garage` or `Building 2 Parking Lot`. " +"This is crucial information for companies with many locations where vehicles" +" are stored." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../content/applications/hr/fleet/new_vehicle.rst:-1 +#: ../../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:212 +msgid "Tax Info tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:214 +msgid "" +"Depending on the localization setting for the database, and what additional " +"applications are installed, other fields may be present on the form." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:217 +msgid "" +"The sections below are default and appear for all vehicles, regardless of " +"other installed applications or localization settings." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:221 +msgid "Fiscality" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:223 +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/new_vehicle.rst:226 +msgid "" +":guilabel:`Disallowed Expenses Rate`: Configure the dates and percentages of" +" the vehicle-related costs (fuel, maintenance, depreciation, etc.) that " +"**cannot** be deducted from the company's taxable income." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:231 +msgid "Contract" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:233 +msgid "" +":guilabel:`First Contract Date`: Select the start date for the vehicle's " +"first contract using the calendar selector. Typically this is the day the " +"vehicle is purchased or leased." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:235 +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/new_vehicle.rst:237 +msgid "" +":guilabel:`Purchase Value`: Enter the purchase price or the original value " +"of the lease for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:239 +msgid ":guilabel:`Residual Value`: Enter the current value of the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:242 +msgid "" +"The values listed above 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:249 +msgid "Model tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:251 +msgid "" +"If the model for the new vehicle is already configured in the database, the " +":guilabel:`MODEL` and :guilabel:`ENGINE` sections are 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:256 +msgid "" +"Check the information in the :guilabel:`Model` tab to ensure it is accurate." +" For example, the color of the vehicle, or if a trailer hitch is installed, " +"are examples of common information that may need updating." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:261 +msgid "Note tab" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:263 +msgid "Enter any notes for the vehicle in this section." +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:269 +msgid ":doc:`../fleet/models`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:270 +msgid ":doc:`../fleet/service`" +msgstr "" + +#: ../../content/applications/hr/fleet/new_vehicle.rst:271 +msgid ":doc:`../fleet/accidents`" +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:9 +msgid "" +"Services, such as regular maintenance, like oil changes or tire rotations, " +"can be logged in advance. Other repairs are logged as they occur." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:15 +msgid "Create service records" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:17 +msgid "" +"To log a service for a vehicle, go to the main :guilabel:`Services` " +"dashboard by navigating to :menuselection:`Fleet app --> Fleet --> " +"Services`. Open a new service form by clicking the :guilabel:`New` button in" +" the top-left corner." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:21 +msgid "" +"Fill out the information on the form. The only two fields that are required " +"to be populated are :guilabel:`Service Type` and :guilabel:`Vehicle`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:24 +msgid "The fields on the form are:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:26 +msgid "" +":guilabel:`Description`: Enter a brief description of the service in this " +"field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:27 +msgid "" +":guilabel:`Service Type`: Using the drop-down menu, select the type of " +"service performed. If the desired service does not exist, enter a new type " +"of service, and click either :guilabel:`Create \"(service type)\"` or " +":guilabel:`Create and edit...` to :ref:`add the service type and configure " +"it `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:33 +msgid "" +"Only one :guilabel:`Service Type` comes preconfigured in Odoo: " +":guilabel:`Vendor Bill`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:35 +msgid "" +":guilabel:`Date`: Using the calendar selector, select the date the service " +"was provided, or is scheduled to be performed. Navigate to the desired month" +" using the :icon:`oi-chevron-left` :icon:`oi-chevron-right` " +":guilabel:`(arrow)` icons, then click on the date to select it." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:38 +msgid "" +":guilabel:`Cost`: Enter the estimated cost of the service, if available. If " +"the service is for a future repair, this field should be left blank. This " +"field is updated as estimates are received, and again, when the final repair" +" cost is known." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:41 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor who is " +"performing the service. If the vendor has not already been entered in the " +"system, :ref:`add and configure the vendor `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:44 +msgid "" +":guilabel:`Vehicle`: Using the drop-down menu, select the vehicle that was " +"serviced. When the vehicle is selected, the :guilabel:`Driver` field is " +"populated, and the unit of measure for the :guilabel:`Odometer Value` field " +"appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:47 +msgid "" +":guilabel:`Driver`: The vehicle's current driver automatically populates " +"this field when the :guilabel:`Vehicle` is selected. If the driver needs to " +"be changed, another driver can be selected using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:50 +msgid "" +":guilabel:`Odometer Value`: Enter the odometer reading from when the service" +" was done. The units of measure are either in kilometers (:guilabel:`km`) or" +" miles (:guilabel:`mi`), depending on how the selected vehicle was " +"configured." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:55 +msgid "" +"To change from kilometers to miles, or vice versa, click the :icon:`oi-" +"arrow-right` :guilabel:`(Internal Link)` icon to the right of the vehicle " +"selected in the :guilabel:`Vehicle` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:59 +msgid "" +"Change the unit of measure, then navigate back to the service form, via the " +"breadcrumb links. The unit of measure is then updated in the " +":guilabel:`Odometer Value` field." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:62 +msgid "" +":guilabel:`NOTES`: Enter any notes for the repair at the bottom of the " +"service form. For example, this can include estimate details or parts being " +"replaced." +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:71 +msgid "Create service type" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:73 +msgid "" +"The **only** method to create service types is from a :ref:`service form " +"`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:75 +msgid "" +"On the :ref:`service form `, type in the name of the new" +" :guilabel:`Service Type` in the corresponding field. Then, click " +":guilabel:`Create and edit...`, and a :guilabel:`Create Service Type` pop-up" +" form appears." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:79 +msgid "" +"The service type entered on the service form automatically populates the " +":guilabel:`Name` field, which can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:82 +msgid "" +"Then, select the :guilabel:`Category` for the new service type from the " +"drop-down menu in that field. The two default options to choose from are " +":guilabel:`Contract` or :guilabel:`Service`. Additional categories " +"**cannot** be created." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:86 +msgid "" +"If the service applies to **only** contracts or services, select the " +"corresponding :guilabel:`Category`. If the service applies to **both** " +"contracts *and* services, leave this field blank." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:90 +msgid "When done, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:95 +msgid "Create vendor" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:97 +msgid "" +"When a service is performed for the first time, typically, the vendor's " +"record has not yet been added to the database. It is best practice to add " +"the full details for a vendor in the database, so that any necessary " +"information can be retrieved." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:101 +msgid "" +"Vendors are added with the **Contacts** app. Refer to the " +":doc:`documentation <../../essentials/contacts>` for more details." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:105 +msgid "" +"Different tabs or fields may be visible on the :guilabel:`Create Vendor` " +"form, depending on what other applications are installed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:109 +msgid "View services" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:111 +msgid "" +"To view all services logged in the database, including old and new requests," +" navigate to :menuselection:`Fleet app --> Fleet --> Services`. All services" +" appear in a list view, including all the details for each service." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:115 +msgid "" +"The service records are grouped by :ref:`service type `. The" +" number of repairs for each service type appears in parentheses after the " +"name of the service type." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:118 +msgid "Each service listed displays the following information:" +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:120 +msgid "" +":guilabel:`Date`: the date that the service, or repair, was performed (or " +"requested to be performed)." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:122 +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:124 +msgid "" +":guilabel:`Service Type`: the type of service, or repair, performed. This is" +" selected from a list of services that :ref:`must be configured `." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:126 +msgid "" +":guilabel:`Vehicle`: the specific vehicle the service was performed on." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:127 +msgid ":guilabel:`Driver`: the current driver for the vehicle." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:128 +msgid "" +":guilabel:`Vendor`: the specific vendor who performed the service, or " +"repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:129 +msgid "" +":guilabel:`Notes`: any information associated with the service, or repair, " +"that is documented to add clarification." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:131 +msgid ":guilabel:`Cost`: the total cost of the service, or repair." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:132 +msgid "" +":guilabel:`Stage`: the status of the service, or repair. Options are " +":guilabel:`New`, :guilabel:`Running`, :guilabel:`Done`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:135 +msgid "" +"At the bottom of the :guilabel:`Cost` column, the total cost of all services" +" and repairs are listed." +msgstr "" + +#: ../../content/applications/hr/fleet/service.rst:-1 +msgid "The full list of services in the Odoo database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:5 +msgid "Frontdesk" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:7 +msgid "" +"The Odoo **Frontdesk** application provides a way for visitors to check in " +"to a building or location, and alert the person they are meeting about their" +" arrival. Additionally, they can request a preconfigured beverage to be " +"brought to them, while they wait." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:11 +msgid "" +"This application is ideal for businesses that do **not** have someone " +"working at a reception desk, or locations **without** a designated waiting " +"area available to guests and visitors." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:17 +msgid "" +"The first item to configure with the **Frontdesk** application is the " +"station, followed by any drink selections that might optionally be offered." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:23 +msgid "Stations" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:25 +msgid "" +"In Odoo's **Frontdesk** application, a *Station* can be thought of as any " +"location where someone can sign in and wait for an employee. This is " +"typically some form of waiting room, such as a lobby. Each station has a " +"kiosk where visitors check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:29 +msgid "" +"When setting up the **Frontdesk** application, a minimum of one station " +"**must** be configured, but there is no limit to how many stations can be " +"created and configured." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:32 +msgid "" +"To create a station, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Stations`, and click :guilabel:`New`. When clicked, a " +"blank frontdesk form appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:37 +msgid "" +":guilabel:`Frontdesk Name`: enter a name for the specific frontdesk " +"location. This should be short and identifiable, such as `Reception Desk` or" +" `Main Lobby`. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:40 +msgid "" +":guilabel:`Responsibles`: select the person (or persons) who are alerted " +"when a visitor checks in using this specific frontdesk. Multiple selections " +"can be entered. This field is required in order to create a station." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:43 +msgid "" +":guilabel:`Kiosk URL`: this field auto-populates once the frontdesk form is " +"saved, with at least the :guilabel:`Frontdesk Name` and " +":guilabel:`Responsibles` fields filled. To save manually, click the " +":icon:`fa-cloud-upload` :guilabel:`(Save manually)` icon located at the top " +"of the form." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:47 +msgid "" +"Once saved, a URL is generated in the :guilabel:`Kiosk URL` field. This URL " +"is one way the frontdesk kiosk is accessed." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:50 +msgid "" +"To access the kiosk, click the :guilabel:`Copy` button at the end of the " +"URL, and navigate to that URL in a web browser. This URL opens that specific" +" station's frontdesk sign-in page." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:54 +msgid "" +"To add an image/photo to a frontdesk form, hover over the :guilabel:`(camera" +" with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:57 +#: ../../content/applications/hr/frontdesk.rst:171 +#: ../../content/applications/hr/frontdesk.rst:186 +msgid "" +"Click on the :icon:`fa-pencil` :guilabel:`(Edit)` icon to open a file " +"explorer, navigate to the desired image/photo file, then click " +":guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:60 +msgid "" +"The image selected for the station photo appears as the background image for" +" the station kiosk." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:63 +msgid "Options tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:67 +msgid "" +":guilabel:`Host Selection`: if the visitor is attending a meeting, this " +"option allows the visitor to select the meeting host from a presented list, " +"and notify that individual. When enabled, additional fields appear, as " +"detailed below." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:70 +msgid "" +":guilabel:`Authenticate Guest`: if additional information is required when a" +" guest checks in, enable this option, and select which of the following are " +"required:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:73 +msgid "" +":guilabel:`Email`: select whether the guest's email address is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:75 +msgid "" +":guilabel:`Phone`: select whether the guest's phone number is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:77 +msgid "" +":guilabel:`Organization`: select whether the guest's organization is " +":guilabel:`Required`, :guilabel:`Optional`, or if the information is not " +"requested at all (:guilabel:`None`)." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:80 +msgid "" +":guilabel:`Theme`: select the color mode of the kiosk. Choose either " +":guilabel:`Light` or :guilabel:`Dark`. The :guilabel:`Light` selection " +"displays a pale gray background on the kiosk, whereas the :guilabel:`Dark` " +"selection displays a dark gray and black background." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:83 +msgid "" +":guilabel:`Self Check-In`: enable this option to present a check-in QR code " +"on the kiosk. The QR code allows guests to check in using their mobile " +"device, instead of using the kiosk. This option is recommended for a busy " +"kiosk with multiple guests checking in at any time." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:86 +msgid "" +":guilabel:`Offer Drinks`: enable this option to offer guests a drink upon " +"check in. If this option is enabled, it is necessary to :ref:`configure the " +"drinks being offered `, via the :guilabel:`Configure " +"Drinks` link that appears when the option is enabled. Once all drink options" +" are configured, select each drink to be offered using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:92 +msgid "" +"The following options are only visible in the :guilabel:`Options` tab if the" +" :ref:`Host Selection ` option is enabled." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:95 +msgid "" +":guilabel:`Notify by email`: enable this option to have an email sent to the" +" person the guest is visiting upon check in. When enabled, an " +":guilabel:`Email Template` field appears beneath, with the default " +":guilabel:`Frontdesk Email Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:99 +msgid "" +"To change the default email template, click the drop-down menu in the " +":guilabel:`Email Template` field, then select another email template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:102 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any edits " +"to the template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:104 +msgid "" +":guilabel:`Notify by SMS`: enable this option to have an SMS (text) message " +"sent to the person the guest is visiting upon check in. When enabled, an " +":guilabel:`SMS Template` field appears beneath, with the default " +":guilabel:`Frontdesk SMS Template` selected." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:108 +msgid "" +"To change the default SMS template, click the drop-down menu in the " +":guilabel:`SMS Template` field, and select another SMS template." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:111 +msgid "" +"To modify the currently selected template, click the :icon:`oi-arrow-right` " +":guilabel:`(Internal link)` icon at the end of the line, and make any " +"desired edits to the content of the template. The SMS message may have a " +"maximum of 242 characters, which fits in 4 SMS (UNICODE) messages." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:114 +msgid "" +":guilabel:`Notify by Discuss`: this option is enabled by default when the " +":guilabel:`Host Selection` option is enabled. This option opens a " +"**Discuss** application message window with the person the guest is visiting" +" upon check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:118 +msgid "" +"When enabled, a default message appears for the person the guest is " +"visiting. The **Discuss** application **must** be installed in order for " +"this option to work." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:122 +msgid "" +"*Discuss* is installed by default when creating an Odoo database, and does " +"not count towards billing. As long as the *Discuss* application is not " +"intentionally uninstalled, the :guilabel:`Notify by Discuss` option works." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:127 +msgid "" +"The default message format for the :guilabel:`Notify by Discuss` option is: " +"`(Frontdesk Station) Check-In: (Guest Name) (Guest Phone Number) " +"(Organization) to meet (Name of employee).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:130 +msgid "" +"An example of how that might appear in a **Discuss** message is: `Main Lobby" +" Check-In: John Doe (555-555-5555) (Odoo, Inc.) to meet Marc Demo.`" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Frontdesk station form with all the information filled out." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:137 +msgid "Side Message tab" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:139 +msgid "" +"Enter any desired text to appear on the station kiosk after a guest has " +"checked in, such as a welcome greeting or any necessary instructions. The " +"text appears on the confirmation page, on the right side of the screen after" +" a guest has completed the check-in process." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:146 +#: ../../content/applications/hr/frontdesk/visitors.rst:139 +msgid "Drinks" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:148 +msgid "" +"After a station is created, the next step is to configure the drinks to " +"offer visitors, if desired." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:151 +msgid "" +"This step is **not** necessary or required for the **Frontdesk** application" +" to work, and only needs to be configured if drinks are offered to guests." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:154 +msgid "" +"To add a drink option, navigate to :menuselection:`Frontdesk app --> " +"Configuration --> Drinks`, and click :guilabel:`New`. Doing so reveals a " +"blank drink form to configure." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:157 +msgid "Enter the following information on the drink form:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:159 +msgid "" +":guilabel:`Drink Name`: type the name of the drink option in this field. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:160 +msgid "" +":guilabel:`People to Notify`: use the drop-down menu in this field to select" +" who is notified when the drink is selected. Multiple people can be entered " +"in this field. This field is required." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:162 +msgid "" +":guilabel:`Sequence`: enter a numerical value in this field to indicate " +"where in the list of drink options this specific option appears. The lower " +"the number, the higher on the list the drink appears. For example, entering " +"the number one would place that drink at the top of the list, and appear " +"first in the sequence." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:168 +#: ../../content/applications/hr/frontdesk.rst:183 +msgid "" +"To add an image/photo to a drink form, hover over the :guilabel:`(camera " +"with a '+' sign)` icon in the top-right of the form to reveal a :icon:`fa-" +"pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:174 +#: ../../content/applications/hr/frontdesk.rst:189 +msgid "" +"The image selected now appears in the picture field, and is set as the image" +" for the drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:-1 +msgid "Drink form with the information filled out for an espresso." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:180 +msgid "Station dashboard" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:194 +msgid "Kiosk setup" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:196 +msgid "" +"Set up each kiosk for use after configuring the various stations. It is " +"recommended to use a dedicated device for each frontdesk kiosk, such as a " +"tablet." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:199 +msgid "Navigate to the kiosk in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:201 +msgid "" +"Navigate to the main **Frontdesk** application dashboard, and click the " +":guilabel:`Open Desk` button on the desired station card. The kiosk loads in" +" a new browser tab." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:203 +msgid "" +"Navigate to :menuselection:`Frontdesk app --> Configuration --> Stations`, " +"and click on the desired station. Then, click the :guilabel:`Copy` button at" +" the end of the :guilabel:`Kiosk URL` line, and paste the URL into a new " +"browser tab or window." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:208 +msgid "" +"Once a frontdesk kiosk is accessed, either with the :guilabel:`Open Desk` " +"button or the :guilabel:`Kiosk URL`, the user is *automatically signed out " +"of the database* on that specific device." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:212 +msgid "" +"This is a security measure designed to prevent unauthorized access to the " +"database." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:215 +#: ../../content/applications/hr/payroll/reporting.rst:3 +#: ../../content/applications/hr/referrals/reporting.rst:3 +#: ../../content/applications/hr/time_off.rst:572 +msgid "Reporting" +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:217 +msgid "" +"The **Frontdesk** application has two reports available: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:220 +msgid "" +"To access either of these reports, navigate to :menuselection:`Frontdesk app" +" --> Reporting` to reveal a drop-down menu containing the options: " +":guilabel:`Visitors` and :guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:223 +msgid "" +"The :guilabel:`Visitors` report displays the number of visitors by month, " +"for the current year. The :guilabel:`Drinks` report shows how many total " +"requests were made for each drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:226 +msgid "" +"As with all reports in Odoo, the filters and groups can be modified to show " +"other metrics, as well." +msgstr "" + +#: ../../content/applications/hr/frontdesk.rst:229 +msgid ":doc:`frontdesk/visitors`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:3 +msgid "Visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:5 +msgid "" +"In the Odoo **Frontdesk** application, a *visitor* refers to any non-" +"employee (e.g., repair person, job candidate, auditor, etc.). Visitor " +"arrivals and departures can be logged for security purposes, ensuring an " +"accurate record of who is on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:12 +msgid "Visitor list" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:14 +msgid "" +"To access a complete list of checked-in visitors, navigate to " +":menuselection:`Frontdesk app --> Visitors`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:18 +msgid "" +"By default, the :guilabel:`Planned or Checked-In` and :guilabel:`Today` " +"filters appear in the :guilabel:`Search...` bar." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:21 +msgid "" +"All visitors are presented in a list view, with the following details that " +"were entered upon check in:" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:24 +msgid ":guilabel:`Name`: the guest's name." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:25 +msgid ":guilabel:`Visitor Company`: the company the guest represents." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:26 +msgid ":guilabel:`Phone`: the guest's phone number." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:27 +msgid ":guilabel:`Drinks`\\*: the drink the guest requested." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:28 +msgid ":guilabel:`Host`: who the guest is waiting to see." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:29 +msgid ":guilabel:`CheckIn`: the date and time the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:30 +msgid "" +":guilabel:`Checkout`\\*: the date and time the guest checked out. In the " +"default view, only guests with a :guilabel:`Checked-In` or " +":guilabel:`Planned` status are visible. Guests with check-out times are only" +" visible if the :guilabel:`Today` filter is removed." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:33 +msgid "" +":guilabel:`Duration`: the amount of time the guest has been checked in for." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:34 +msgid ":guilabel:`Station`: the location of where the guest checked in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:35 +msgid "" +":guilabel:`Status`: the status of the guest. The options are " +":guilabel:`Checked-In`, :guilabel:`Planned`, :guilabel:`Checked-Out`, or " +":guilabel:`Cancelled`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:37 +msgid ":guilabel:`Email`\\*: the guest's email address." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:38 +msgid "" +":guilabel:`Company`\\*: the company the guest is there to visit. This field " +"is only available if in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:41 +msgid "" +"\\* These fields are not visible in the default :guilabel:`Visitor` list. " +"These must be enabled using the :icon:`oi-settings-adjust` " +":guilabel:`(adjust settings)` icon in the top-right corner of the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:45 +msgid "" +"To the far-right of the titled columns on the :guilabel:`Visitors` page, " +"there is an untitled column, where a guest's status can be updated." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:48 +msgid "" +"When a guest leaves, click the available :guilabel:`Check out` button to " +"update the guest's record, and log the date and time they left." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:51 +msgid "" +"If a scheduled guest arrives, and they did not check in using a " +"**Frontdesk** kiosk, they can be checked in from this list, by clicking the " +"available :guilabel:`Check in` button to log the date and time they arrived." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:55 +msgid "" +"Beside the untitled status column, a :guilabel:`Drink Served` button " +"appears, but only if that particular visitor requested a drink." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:58 +msgid "" +"When their drink has been served, click the :guilabel:`Drink Served` button " +"to indicate the drink has been delivered to the guest. Once clicked, that " +"button disappears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:61 +msgid "" +"On the far-right of the line, a :guilabel:`Print Badge` button appears for " +"*planned* visitors **only**. Click this button to download a PDF file of the" +" visitor's badge. The badge displays the date and time the visitor checked " +"in, the visitor's name and company, who they are visiting, and the logo of " +"the company they are visiting." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:67 +msgid "" +"The PDF badge can be printed onto adhesive labels for the visitor to wear, " +"or onto paper that can be placed into a plastic badge holder." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:-1 +msgid "" +"The full list of currently checked in visitors, with the drinks to be served" +" highlighted." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:73 +msgid "" +"If any column is not visible, or if a visible column is preferred to be " +"hidden, click the :icon:`oi-settings-adjust` :guilabel:`(adjust settings)` " +"icon, located at the end of the top line. Doing so, reveals a drop-down menu" +" of column options to enable or disable. A :icon:`fa-check` " +":guilabel:`(check)` icon indicates the column is visible." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:81 +msgid "Planned visitors" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:83 +msgid "" +"When guests are expected, such as job candidates, government officials, or " +"new suppliers, it can be helpful to enter the visitor information in " +"advance. When the visitors arrive, they can utilize the *Quick Check In* " +"option on the kiosk, rather than entering all their information manually " +"upon arrival." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:88 +msgid "" +"Enter expected guest information in advance by creating a planned guest in " +"the **Frontdesk** app." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:90 +msgid "" +"To create a planned guest, navigate to :menuselection:`Frontdesk app --> " +"Visitors`, and click :guilabel:`New`. Then, enter the same information as " +"any other :ref:`visitor ` on the guest form that appears. " +"The only required fields are the visitor's :guilabel:`Name` and the " +":guilabel:`Station` at which they are expected to arrive." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:96 +msgid "" +"If a guest is planned in advance, they must be checked in from the list on " +"the :guilabel:`Visitors` page in the **Frontdesk** application " +"(:menuselection:`Frontdesk app --> Visitors`). If a planned guest checks in " +"using a kiosk, they are checked in separately from their planned visitor " +"entry, and their planned visitor entry remains listed as " +":guilabel:`Planned`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:101 +msgid "" +"The :guilabel:`Planned` status of a planned guest **only** changes to " +":guilabel:`Checked-In` when they are checked in *inside* the application's " +":guilabel:`Visitors` list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:104 +msgid "" +"If a guest does check in using a kiosk, ensure all records are current, and " +"the list of guests that are currently on-site is correct. Be sure to check " +"in and/or check out the correct entries, so the visitors list correctly " +"reflects who is currently on the premises." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:108 +msgid "" +"Ensure planned guests are informed that they should **not** check in using " +"the kiosk if they are listed as a planned guest in advance." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:112 +msgid "Visitor flow" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:115 +msgid "Visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:117 +msgid "" +"When a visitor arrives at a facility, they approach a :ref:`Frontdesk kiosk " +"`, and click :guilabel:`Check in`. The information " +"requested from the visitor is what was configured for that specific " +"**Frontdesk** station. If any information is required, the field displays a " +"red asterisk (\\*). The visitor **must** enter the required information in " +"order to check in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:122 +msgid "" +"Once all the information is entered, the visitor taps the :guilabel:`Check " +"In` button." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:125 +msgid "" +"At any point in the check-in process, if ten seconds pass with no selection," +" the kiosk returns to the main welcome screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:129 +msgid "Planned visitor check in" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:131 +msgid "" +"When a :ref:`planned visitor ` arrives at a facility, " +"they first approach a :ref:`Frontdesk kiosk `. If there are" +" planned visitors for that day, a :guilabel:`Quick Check In` panel appears " +"on the right-side of the kiosk, asking :guilabel:`Are you one of these " +"people?` Beneath the question is a list of all visitors schedule to arrive " +"that day." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:136 +msgid "Click on the corresponding name in the list to check-in." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:141 +msgid "" +"If drinks were configured for the station, after tapping :guilabel:`Check " +"In`, a registration confirmation screen loads, along with the question: " +":guilabel:`Do you want something to drink?`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:144 +msgid "" +"The visitor can tap either :guilabel:`Yes, please`, or :guilabel:`No, thank " +"you`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:146 +msgid "" +"If they select :guilabel:`Yes, please`, a drink selection screen appears, " +"and the preconfigured options are listed. The visitor then taps the desired " +"selection, or, if they do not want anything, they can tap the " +":guilabel:`Nothing, thanks` button at the bottom of the screen." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:150 +msgid "" +"If a drink selection was made, a :guilabel:`Thank you for registering! Your " +"drink is on the way.` message appears." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:154 +msgid "Notifications" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:156 +msgid "" +"Once the visitor has checked in, the person they are visiting, and any other" +" users who were configured to be notified when check-ins occur at the kiosk," +" are notified. The notification is either by email, SMS message, a *Discuss*" +" chat, or any combination of those three options." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:160 +msgid "" +"If the visitor requested a drink, the users configured as the " +":guilabel:`People to Notify` on the drink form are notified, via the " +"*Discuss* application. The message that appears is: :guilabel:`(Visitor " +"Name) just checked-in. They requested (Drink Name).`" +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:164 +msgid "" +"Once the drink has been delivered to the guest, the person who delivered the" +" drink is responsible for marking the drink as delivered." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:167 +msgid "" +"To mark a drink as delivered, navigate to :menuselection:`Frontdesk app --> " +"Stations`, and choose the desired station card displaying :guilabel:`(#) " +"Drinks to serve`." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:170 +msgid "" +"This opens a list of all the visitors checked in at that station, and are " +"waiting for a drink. Click the :guilabel:`Drink Served` button at the end of" +" the line for the visitor who was served. Once they are marked as having " +"their drink served, the visitor disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:177 +msgid "" +"Once the visitor has completed their business, and has left the premises, it" +" is important to check them out for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:180 +msgid "" +"To check visitors out properly, navigate to :menuselection:`Frontdesk app " +"--> Stations`, and choose the desired station card displaying :guilabel:`(#)" +" Drinks to serve`. Doing so opens a list of all the visitors who are " +"currently checked-in at that station." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:184 +msgid "" +"Click the :guilabel:`Check out` button near the end of the line for the " +"visitor who left. Once they are marked as checked-out, the visitor " +"disappears from the list." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:188 +msgid "" +"Visitors do **not** check themselves out when they leave. It is important " +"for **Frontdesk** users to check out visitors for accurate record keeping." +msgstr "" + +#: ../../content/applications/hr/frontdesk/visitors.rst:191 +msgid "" +"Always have an accurate list of who is on the premises at any given time. " +"This is important for security purposes, and in the case of an emergency." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:5 +msgid "Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:7 +msgid "" +"The **Lunch** application in Odoo allows users to conveniently order food " +"and pay for their meal directly from the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:10 +msgid "" +"Before employees can use the **Lunch** application, there are a number of " +"configurations that need to be made: :ref:`settings `, " +":doc:`vendors `, :ref:`locations `, " +":doc:`products `, and :ref:`product categories " +"`. Once these are created and configured, " +"employees can view offerings and order food." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:21 +msgid "" +"In the :guilabel:`Settings` menu, only two items need to be configured: " +"overdraft settings and notifications. To access the settings, navigate to " +":menuselection:`Lunch app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:25 +msgid "Configure the following:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:27 +msgid "" +":guilabel:`Lunch Overdraft`: enter the maximum overdraft amount for " +"employees. The currency format is determined by the localization setting of " +"the company." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:29 +msgid "" +":guilabel:`Reception notification`: set the message users receive via the " +"**Discuss** app when their food has been delivered. The default message " +"`Your lunch has been delivered. Enjoy your meal!` populates this field, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:34 +msgid "" +"If a database has multiple languages installed, many forms in the **Lunch** " +"application have the option of entering translations for various fields." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:37 +msgid "" +"If translations are available to be configured, a language code appears next" +" to a translatable field on a form. To add translations for that field, " +"click the two letter language code (for example, :guilabel:`EN` for English)" +" and a translation pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:41 +msgid "" +"The following is an example for the :guilabel:`Reception notification` field" +" in the settings menu:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:44 +msgid "" +"Navigate to :menuselection:`Lunch app --> Configuration --> Settings`. Click" +" the :guilabel:`EN` In the top-right of the text box beneath the " +":guilabel:`Reception notification` section. A :guilabel:`Translate: " +"company_lunch_notify_message` pop-up window loads with the option to enter a" +" translation for the other languages used by the database." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:49 +msgid "" +"The first column lists the different languages in alphabetical order, with " +"the currently selected language in bold. The second column has the currently" +" configured message in each column. The last column in the far-right " +"provides a text box to type in a translation for each language." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:53 +msgid "" +"Enter the text that should appear for each language, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:0 +msgid "" +"The translation text box, with the current language highlighted, and the Arabic\n" +"translation field highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:62 +msgid "Locations" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:64 +msgid "" +"By default, Odoo creates an `HQ Office` location when the **Lunch** " +"application is installed. If a company has more than one location, they must" +" be configured." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:67 +msgid "" +"To add a location, navigate to :menuselection:`Lunch app --> Configuration " +"--> Locations`. The currently configured locations appear in a list view. " +"Click the :guilabel:`New` button in the top-left corner and a blank line " +"appears beneath the last location in the list." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:71 +msgid "" +"Enter the name of the location in the field. Next, click into the " +":guilabel:`Address` field to the right of the name, and enter the location's" +" address. It is possible to enter multiple lines in the address field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:75 +msgid "Repeat this for all locations that need to be added." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "A list view of the locations with the new button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:81 +#: ../../content/applications/hr/referrals/alerts.rst:3 +msgid "Alerts" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:83 +msgid "" +"It is possible to set up alerts that can either be displayed in the " +"**Lunch** app, or be sent to specific employees via the **Discuss** app." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:86 +msgid "" +"No alerts are preconfigured by default. To set up an alert, navigate to " +":menuselection:`Lunch app --> Configuration --> Alerts`. Click the " +":guilabel:`New` button in the top-left corner and a blank lunch alert form " +"loads. Enter the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:90 +msgid "" +":guilabel:`Alert Name`: enter a name for the alert. This should be short and" +" descriptive, such as `New Lunch Vendor` or `Order by 11:00 AM`. This field " +"is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:92 +msgid "" +":guilabel:`Display`: select whether the alert is visible in the **Lunch** " +"app (:guilabel:`Alert in app)` or sent to employees via the **Discuss** app " +"in a chat window (:guilabel:`Chat notification`)." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:96 +msgid "" +":guilabel:`Recipients`: this field only appears if :guilabel:`Chat " +"notification` is selected for the :guilabel:`Display` option. Select who " +"receives the chat alert. The options are: :guilabel:`Everyone`, " +":guilabel:`Employee who ordered last week`, :guilabel:`Employee who ordered " +"last month`, or :guilabel:`Employee who ordered last year`." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:101 +msgid "" +":guilabel:`Location`: select the locations the alert should appear for from " +"the drop-down menu. Multiple locations can be selected. This field is " +"**required**, therefore, if the alert applies to all locations, select all " +"the locations from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:104 +msgid "" +":guilabel:`Show Until`: if the alert should expire on a specific date, " +"select the date from the calendar picker." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:106 +msgid "" +":guilabel:`Active`: this option is on (appears green) by default. To turn " +"off the alert, click the toggle so that it no longer appears green." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:108 +msgid "" +":guilabel:`Message`: Enter the alert message in this field. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:109 +msgid "" +":guilabel:`Notification Time`: select the days of the week the alert should " +"be sent. By default, all seven days are active. Click on a checkbox to " +"change the setting from active to inactive." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:112 +msgid "" +"If :guilabel:`Chat notification` was selected for the :guilabel:`Display` " +"option, a :guilabel:`Time` field also appears. Enter the time the chat " +"message should be sent. Next, select if the time is either :guilabel:`AM` or" +" :guilabel:`PM` using the drop-down menu to the right of the " +":guilabel:`Time` field." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:-1 +msgid "" +"An alert form with all of the information filled out for a chat alert sent at 10:30 AM,\n" +"asking employees to submit orders by 11:30 AM." +msgstr "" + +#: ../../content/applications/hr/lunch.rst:122 +msgid ":doc:`lunch/vendors`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:123 +msgid ":doc:`lunch/products`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:124 +msgid ":doc:`lunch/orders`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:125 +msgid ":doc:`lunch/user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch.rst:126 +msgid ":doc:`lunch/management`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:3 +msgid "Lunch management" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:5 +msgid "" +"In Odoo's **Lunch** application, it is required to have someone manage the " +"orders, vendors, and products. In addition, someone must be responsible for " +"the orders, and notifying employees when their orders have arrived. This can" +" be the same person." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:9 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified `, either from the " +":ref:`Today's Orders ` dashboard, or the :ref:`Control " +"Vendors ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:14 +msgid "" +"To manage the **Lunch** app, users need the appropriate " +":guilabel:`Administrator` rights. These can be set by navigating to the " +":menuselection:`Settings app` and selecting :guilabel:`Manage Users`. Then, " +"click on the desired user to view their access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:18 +msgid "" +"For more information on access rights, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:22 +msgid "" +"Only users with administration rights are able to view the " +":guilabel:`Manager` and :guilabel:`Configuration` menus in the **Lunch** " +"application." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:28 +msgid "Today's Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:30 +msgid "" +"To view and manage the orders for the day, navigate to :menuselection:`Lunch" +" app --> Manager --> Today's Orders`. All orders for the day are presented " +"in a list view on the :guilabel:`Today's Orders` dashboard, with a filter " +"for :guilabel:`Today`, and grouped by :guilabel:`Vendor`, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:35 +#: ../../content/applications/hr/lunch/management.rst:157 +msgid "The following information appears in the list:" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:37 +#: ../../content/applications/hr/lunch/management.rst:159 +msgid ":guilabel:`Order Date`: the date the order was placed." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:38 +#: ../../content/applications/hr/lunch/management.rst:160 +msgid ":guilabel:`Vendor`: the vendor the product is being ordered from." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:39 +#: ../../content/applications/hr/lunch/management.rst:161 +msgid ":guilabel:`Product`: the specific product ordered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:40 +#: ../../content/applications/hr/lunch/management.rst:162 +msgid ":guilabel:`Extras`: any extras selected for the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:41 +#: ../../content/applications/hr/lunch/management.rst:163 +msgid ":guilabel:`Notes`: any information needed to be sent to the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:42 +#: ../../content/applications/hr/lunch/management.rst:164 +msgid ":guilabel:`User`: the user who ordered the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:43 +#: ../../content/applications/hr/lunch/management.rst:165 +msgid ":guilabel:`Lunch Location`: where the product is set to be delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:44 +#: ../../content/applications/hr/lunch/management.rst:166 +msgid "" +":guilabel:`Price`: the total price for the product, including all extras." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:45 +#: ../../content/applications/hr/lunch/management.rst:167 +msgid ":guilabel:`Status`: the current status of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:46 +#: ../../content/applications/hr/lunch/management.rst:168 +msgid "" +":guilabel:`Company`: the company under which the order was placed. This only" +" appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The list that appears in the Today's Orders dashboard, with the filters and top column\n" +"names highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:56 +msgid "Cancel orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:58 +msgid "All users can cancel an order, not only managers of the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:60 +msgid "" +"To cancel an order from a vendor, individual products **must** be cancelled " +"one at a time." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:62 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, a :icon:`fa-times` " +":guilabel:`Cancel` button is shown at the far-right of each product line " +"that can be cancelled. Click the :icon:`fa-times` :guilabel:`Cancel` button " +"to cancel the order for that individual product." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:67 +msgid "" +"Only products with a red :guilabel:`Status` tag of :guilabel:`Ordered` can " +"be cancelled." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "Order lines with the cancel button highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:75 +msgid "Send orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:77 +msgid "" +"The first step in managing the **Lunch** app is to send the orders to the " +"vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:79 +msgid "" +"When orders are ready to be sent, the manager responsible for sending orders" +" **must** send the orders to the vendor, outside of the database (call, " +"online order, etc.)." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:82 +msgid "" +"Once orders have been placed with the vendors, click the :guilabel:`Send " +"Orders` button that appears next to each vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:85 +msgid "" +"Once sent, the :guilabel:`Send Orders` button changes to a " +":guilabel:`Confirm Orders` button, and the :guilabel:`Status` column is " +"updated from red :guilabel:`Ordered` tags to blue :guilabel:`Sent` tags, " +"indicating the order has been sent to the vendor. Users who have placed " +"orders in the **Lunch** app rely on the :guilabel:`Status` tags to track " +"their orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A vendor's order with the X Cancel and Send Orders buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:96 +msgid "Confirm orders" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:98 +msgid "" +"After orders have been sent to the vendor, the next step is to confirm the " +"orders after they have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:101 +msgid "" +"On the :guilabel:`Today's Orders` dashboard, click the :guilabel:`Confirm " +"Orders` button that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:104 +msgid "" +"Once confirmed, the :guilabel:`Confirm Orders` button disappears, and the " +":guilabel:`Status` column is updated from blue :guilabel:`Sent` tags to " +"green :guilabel:`Received` tags, indicating the vendor has delivered the " +"orders." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:108 +msgid "" +"In addition, the :icon:`fa-times` :guilabel:`Cancel` button at the end of " +"each product line changes to a :icon:`fa-envelope` :guilabel:`Send " +"Notification` button." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:111 +msgid "" +"If needed, instead of confirming all of the individual products from a " +"vendor, individual products can be confirmed one at a time. To confirm an " +"individual product, click the :icon:`fa-check` :guilabel:`Confirm` button at" +" the end of the individual product line. When confirming individual products" +" with this method, the :guilabel:`Confirm Orders` button remains on the " +"vendor line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"The Today's Orders dashboard, with the two different ways to confirm an " +"order highlighted." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:120 +msgid "" +"A vendor receives an order for three pizzas, and an order of garlic knots. " +"When the delivery is made to the company, the **Lunch** manager notices the " +"garlic knots are missing." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:123 +msgid "" +"The manager first marks the three pizzas as received, by individually " +"confirming the products with the :icon:`fa-check` :guilabel:`Confirm` " +"button at the end of each product line." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:126 +msgid "" +"Later, when the vendor delivers the garlic knots, the manager can either " +"click the :icon:`fa-check` :guilabel:`Confirm` button at the end of the " +"line for the garlic knots, or click the :guilabel:`Confirm Orders` button " +"that appears next to the vendor's name and phone number." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:134 +msgid "Notify employees" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:136 +msgid "" +"After products are received, and the orders are confirmed, the employees " +"**must** be informed that their orders have been delivered, and are ready to" +" be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:139 +msgid "" +"Unlike sending and confirming orders, notifications must be sent " +"individually, and cannot be sent in a batch." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:142 +msgid "" +"To notify the user their product has arrived, click the :icon:`fa-envelope` " +":guilabel:`Send Notification` button at the end of each product line. An " +"email is sent to the user informing them their products have been delivered." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:149 +msgid "Control Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:151 +msgid "" +"All orders for all vendors, both past and present, can be found in the " +"*Control Vendors* dashboard. To access these records, navigate to " +":menuselection:`Lunch app --> Manager --> Control Vendors`." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:154 +msgid "" +"All orders appear in a list view, grouped alphabetically by " +":guilabel:`Vendor`. The list loads with all vendors expanded to show all " +"order lines for every vendor, by default." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:171 +msgid "" +"Orders can be :ref:`cancelled `, :ref:`sent to the vendor " +"`, :ref:`confirmed ` upon arrival, " +"and :ref:`employees can be notified ` using the same method as" +" on the :ref:`Today's Orders ` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:-1 +msgid "" +"A list view of all the orders as seen in the Control Vendors dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:180 +msgid "" +"The difference between the :ref:`Today's Orders ` " +"dashboard and the :ref:`Control Vendors ` dashboard " +"is that the *Today's Orders* dashboard **only** displays orders for the " +"current day, while the :guilabel:`Control Vendors` dashboard displays " +"**all** orders made in the **Lunch** app." +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:186 +msgid ":doc:`../lunch`" +msgstr "" + +#: ../../content/applications/hr/lunch/management.rst:187 +msgid ":doc:`user-accounts`" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:5 +#: ../../content/applications/hr/lunch/vendors.rst:75 +msgid "Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:7 +msgid "" +"The **Lunch** app lets employees place lunch orders, see what's available " +"each day, and check their account balance, all from one place." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:10 +msgid "" +"When the **Lunch** application is opened, the :guilabel:`Order Your Lunch` " +"dashboard loads. This view is also accessible by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:13 +msgid "" +"The :guilabel:`Order Your Lunch` dashboard provides a summary of lunch " +"offerings, the user's account information, and the current day's orders, " +"along with their statuses." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:17 +msgid "Order Your Lunch" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:19 +msgid "" +"On the main :guilabel:`Order Your Lunch` dashboard, all the necessary " +"information needed to place an order is visible. Enable the " +":guilabel:`Available Today` filter in the search bar by clicking into the " +"search bar and selecting :guilabel:`Available Today`. This filter shows only" +" products that can be purchased that day, based on the :ref:`vendor's " +"availability `." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:24 +msgid "" +"The left-side of the dashboard displays the various :guilabel:`Categories` " +"of products available, along with the :guilabel:`Vendors` supplying the " +"products. To the right of each line is a number, which indicates how many " +"products are associated with that respective category or vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:28 +msgid "" +"To filter the products by categories or vendors, tick the checkbox next to " +"the desired category or vendor to only view items related to those " +"selections. Multiple selections can be made in each section." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:33 +msgid "" +"If multiple selections are made, **only** products that fall under **all** " +"the selected options are shown." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:36 +msgid "" +"The top portion of the dashboard, which serves as an order summary, displays" +" the user's account information, and the order details for today, if any " +"orders have been placed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:39 +msgid "" +"The main section, beneath the user's information, displays all the products " +"in a default Kanban view. Each product card displays the name, cost, vendor," +" photo, and description of the product. If the product is configured as new," +" it also displays a :guilabel:`New` tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The Lunch app dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:47 +msgid "" +"Anywhere a vendor's name is listed in the **Lunch** app, such as on Kanban " +"product cards, their phone number is listed, as well." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:50 +msgid "" +"The products can also be displayed in a list view, by clicking the " +":icon:`oi-view-list` :guilabel:`(List)` icon in the top-right corner of the " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:54 +msgid "Placing orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:56 +msgid "" +"To place a lunch order, navigate to the main :guilabel:`Order Your Lunch` " +"dashboard, by either opening the **Lunch** app, or by navigating to " +":menuselection:`Lunch app --> My Lunch --> New Order`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:61 +msgid "Add products to an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:63 +msgid "" +"From the :guilabel:`Order Your Lunch` dashboard, click on a desired product " +"to add to an order, and the product appears in a :guilabel:`Configure Your " +"Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:66 +msgid "" +"At the top of the pop-up window is the product image, name, and price. " +"Beneath that, there are potential :guilabel:`Extras` fields, showcasing any " +":ref:`extra items or options `, such as toppings or drinks. " +"Tick the checkbox next to any desired extras present in the " +":guilabel:`Extras` fields to add them to the order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:71 +msgid "" +"Each extra option is organized by a category, complete with its name and " +"price. As extras are selected, the displayed price at the top of the pop-up " +"window updates to reflect all current selections." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:75 +msgid "" +"Beneath the :guilabel:`Extras` field is the :guilabel:`Description` of the " +"product, followed by a :guilabel:`Notes` field. The :guilabel:`Notes` field " +"is used to enter any vital information, which is then sent to the vendor " +"regarding the order, such as any special requests or food allergies." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:79 +msgid "" +"When all selections for the product have been made, click the :guilabel:`Add" +" To Cart` button in the lower-left of the pop-up window. To cancel the " +"order, click the :guilabel:`Discard` button." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The pop-up window for a personal pizza, with all the extras selected." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:88 +msgid "" +"Depending on how the various :ref:`extras ` are " +"configured for a vendor, it is possible to receive an error when attempting " +"to add products to the cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:91 +msgid "" +"An error can occur when a configured product **requires** the user to select" +" an option in the :guilabel:`Extras` field, but the user neglects to make " +"one." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:94 +msgid "" +"When this occurs, a :guilabel:`Validation Error` pop-up window appears. The " +"error is briefly explained in the pop-up window. Click :guilabel:`Close` to " +"close the window, and make any necessary changes to the :guilabel:`Configure" +" Your Order` pop-up window." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:99 +msgid "" +"The vendor, The Pizza Palace, provides a free beverage with any purchase. " +"Their products are configured so that a beverage selection is **required** " +"in the :guilabel:`Extras` field *before* adding one of their products to the" +" cart." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:103 +msgid "" +"If a selection is **not** made, an error occurs. The message that appears is" +" `You have to order one and only one Free Beverage with Purchase`." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:0 +msgid "" +"The :guilabel:`Validation Error` pop-up window with the specific error for the free\n" +"beverage displayed." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:111 +msgid "Your Order summary" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:113 +msgid "" +"When at least one item is added to an order, the items appear at the top of " +"the dashboard in the :guilabel:`Your Order` summary. In addition to the " +"products, users can view the account information, in addition to all the " +"information related to orders placed during the current calendar day." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:117 +msgid "" +"As products are added to an order, they appear at the top center of the " +"summary box. Each product is listed beneath the words :guilabel:`Your " +"Order`, with the product name, quantity, and a status tag." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:120 +msgid "The available tags that can be displayed for each item are:" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:122 +msgid "" +":guilabel:`To Order`: the product has been added to the cart, but has not " +"been purchased yet by the user." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:124 +msgid "" +":guilabel:`Ordered`: the product has been purchased by the user, and is " +"waiting to be sent to the vendor by a **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:126 +msgid "" +":guilabel:`Sent`: the order for the product has been sent to the vendor by a" +" **Lunch** app manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:128 +msgid "" +":guilabel:`Received`: the product has been delivered by the vendor to the " +"user's location, and has been verified as received by a **Lunch** app " +"manager." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:131 +msgid "" +"Product quantities can be adjusted by clicking the :icon:`fa-plus` " +":guilabel:`(plus)` or :icon:`fa-minus` :guilabel:`(minus)` icons to the left" +" of the listed product. The product price adjusts in real-time to display " +"the cost for the currently selected quantity of the product." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:135 +msgid "" +"The right side of the :guilabel:`Your Order` summary displays the purchasing" +" information. The :guilabel:`Total` amount for the entire day's lunch order " +"is displayed. The :guilabel:`Already Paid` field indicates how much has been" +" paid that day towards the :guilabel:`Total` amount. The :guilabel:`To Pay` " +"field displays how much of the remaining :guilabel:`Total` amount must be " +"paid, in order to place the currently configured order." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'Your Orders' section of the dashboard, with purchasing information." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:145 +msgid "" +"Users can place multiple orders throughout the day, and are not restricted " +"to only placing one lunch order each day. Multiple orders might need to be " +"placed, due to users forgetting to add items to an order, or if there are " +"multiple meals that are available to be purchased for the office (not only " +"lunch), and so on." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:150 +msgid "" +"Depending on the various vendors, and how the vendors and products are " +"configured, it is possible to order breakfast, lunch, dinner, coffee, and/or" +" snacks." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:154 +msgid "Submit an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:156 +msgid "" +"To place the order, click the :guilabel:`Order Now` button on the right-side" +" of the :guilabel:`Your Order` summary. The user is charged the amount that " +"is displayed in the :guilabel:`To Pay` field, and the cost is deducted from " +"their **Lunch** account balance." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:160 +msgid "" +"Once the order is placed, the tags for the purchased items in the " +":guilabel:`Your Order` field change from orange :guilabel:`To Order` tags to" +" red :guilabel:`Ordered` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:164 +msgid "Track an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:166 +msgid "" +"When orders have been sent to the vendors, the tags for the items in the " +":guilabel:`Your Order` summary change from red :guilabel:`Ordered` tags to " +"blue :guilabel:`Sent` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:169 +msgid "" +"Once orders have been received and verified, the tags change from blue " +":guilabel:`Sent` tags to green :guilabel:`Received` tags." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:173 +msgid "Receive an order" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:175 +msgid "" +"When orders are received at the delivery location, they are confirmed by a " +"**Lunch** app manager, and a notification is sent to the employee who " +"ordered the food." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:179 +msgid "My Orders" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:181 +msgid "" +"To view a full list of all orders placed in the **Lunch** app for the " +"currently signed-in user, navigate to :menuselection:`Lunch app --> My Lunch" +" --> My Order History`. This navigates to the :guilabel:`My Orders` " +"dashboard. The data is filtered by :guilabel:`My Orders` and grouped by " +":guilabel:`Order Date: Day`, by default, both of which are located in the " +"search bar." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:186 +msgid "" +"All products appear in a list view, organized by date. The list displays the" +" :guilabel:`Order Date`, :guilabel:`Vendor`, :guilabel:`Product`, " +":guilabel:`Extras`, :guilabel:`Notes`, :guilabel:`User`, :guilabel:`Lunch " +"Location`, :guilabel:`Price`, and :guilabel:`Status` information. If in a " +"multi-company database, a :guilabel:`Company` column also appears." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:191 +msgid "" +"The total cost for each order is displayed on the line containing the order " +"date. At the bottom of the list, beneath all the lines, the overall total " +"amount paid for all the orders appears, under the :guilabel:`Price` column." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:195 +msgid "" +"At the end of each product line with a status of :guilabel:`Ordered` or " +":guilabel:`Sent`, an :guilabel:`X Cancel` button appears. Click :guilabel:`X" +" Cancel` to cancel that product order. Once a product order has been " +"cancelled, the money paid for that product is refunded, and appears in the " +"user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:200 +msgid "" +"At the end of each product line with a status of :guilabel:`Received`, a " +":guilabel:`Re-order` button appears. Click :guilabel:`Re-order` to instantly" +" reorder that same product, with the same extras, if applicable. The new " +"order appears in the list, under the current date, and the product is paid " +"for, with money deducted from the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "The list view that appears when navigating to the My Orders dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:209 +msgid "My Account" +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:211 +msgid "" +"To view a summary of all transactions in the user's account, navigate to " +":menuselection:`Lunch app --> My Lunch --> My Account History`. Doing so " +"reveals the :guilabel:`My Account` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:214 +msgid "" +"The default presentation of the :guilabel:`My Account` dashboard displays " +"all entries, from newest to oldest. The :guilabel:`Date`, " +":guilabel:`Description`, and :guilabel:`Amount` are the only fields " +"displayed in the list." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:218 +msgid "" +"Entries with a negative figure listed in the :guilabel:`Amount` column " +"represent products purchased in the **Lunch** app. These appear in a " +"`$-XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:221 +msgid "" +"Entries with a positive balance either represent funds added to the user's " +"lunch account, or cancelled orders that were eventually refunded to the " +"user. These appear in a `$XX.XX` format." +msgstr "" + +#: ../../content/applications/hr/lunch/orders.rst:-1 +msgid "" +"The 'My Account' dashboard with the entry for adding funds to the user's " +"lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:3 +msgid "Products" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:5 +msgid "" +"Odoo's **Lunch** app does *not* come with any products preconfigured. The " +"individual products being offered must first be configured before orders can" +" be placed." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:8 +msgid "" +"To add and configure products for the **Lunch** app, navigate to " +":menuselection:`Lunch app --> Configuration --> Products`. Next, click the " +":guilabel:`New` button in the top-left corner, and a blank product form " +"loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:14 +msgid "" +":guilabel:`Product Name`: Enter the name for the product. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:15 +msgid "" +":guilabel:`Product Category`: Using the drop-down menu, select the " +":ref:`category ` this product falls under. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:17 +msgid "" +":guilabel:`Vendor`: Using the drop-down menu, select the vendor that " +"supplies this product. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:19 +msgid "" +":guilabel:`Price`: Enter the price for the product. The currency is " +"determined by the company's localization." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:21 +msgid "" +":guilabel:`Description`: Enter a description of the product in this field. " +"This description appears beneath the product photo when users are viewing " +"the day's options." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:23 +msgid "" +":guilabel:`New Until`: Using the calendar popover, select the date on which " +"the product is no longer labeled as new. Until this date, a green `New` tag " +"appears on the product." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:25 +msgid "" +":guilabel:`Company`: Using the drop-down menu, select the companies this " +"product is available for. If this field is left blank, this product does " +"**not** appear for **any** company." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:27 +msgid "" +"**Image**: Hover over the image box in the top-right corner of the form, and" +" click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that appears. A file " +"explorer pop-up window appears. Navigate to the image, then click " +":guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "A product form filled out for a nine inch pizza." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:37 +msgid "Product categories" +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:39 +msgid "" +"Product categories organize the offerings in the **Lunch** app, and allows " +"users to filter offerings when reviewing the menu for the day." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:42 +msgid "" +"To add or modify categories, navigate to :menuselection:`Lunch app --> " +"Configuration: Product Categories`. The available categories appear in a " +"list view." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:45 +msgid "" +"In the **Lunch** app, there are four default categories: " +":guilabel:`Sandwich`, :guilabel:`Pizza`, :guilabel:`Burger`, and " +":guilabel:`Drinks`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:48 +msgid "" +"To add a new category, click the :guilabel:`New` button in the top-left " +"corner, and a blank category form loads." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:51 +msgid "" +"Enter a name in the :guilabel:`Product Category` field. If the category is " +"company-specific and should only appear for a certain company, select the " +":guilabel:`Company` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:54 +msgid "" +"If desired, add a photo for the category. Hover over the image box in the " +"top-right, and click the :icon:`fa-pencil` :guilabel:`(pencil)` icon that " +"appears. This opens a file explorer pop-up window. Navigate to the image, " +"then click :guilabel:`Open`." +msgstr "" + +#: ../../content/applications/hr/lunch/products.rst:-1 +msgid "The category form, with the fields filled out for a Soup category." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:3 +msgid "Manage user accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:5 +msgid "" +"In Odoo's **Lunch** application, users pay for products directly from their " +"**Lunch** app account. For funds to appear in their account, a **Lunch** app" +" manager **must** transfer funds into each user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:10 +msgid "" +"To add funds and manage user accounts, the user must have " +":guilabel:`Administrator` access rights set for the **Lunch** application. " +"This is verified by navigating to :menuselection:`Settings app -->` " +":icon:`oi-arrow-right` :guilabel:`Manage Users`. Then, click on a user to " +"view their various settings and access rights." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:15 +msgid "" +"For more information, refer to the :doc:`Access rights " +"<../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:18 +msgid "" +"The **Lunch** application does **not** directly interface in any way with " +"software or products linked to any monetary accounts or billing. Money " +"**cannot** be transferred from users' bank accounts, nor can users' credit " +"cards be charged." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:22 +msgid "" +"Odoo's **Lunch** application **only** allows for manual entries of cash " +"exchanges that are handled by the **Lunch** app manager. It is up to each " +"individual company to create the method with which lunch accounts are " +"replenished." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:27 +msgid "" +"Some examples of how money can be organized and transferred within a " +"company:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:29 +msgid "" +"Cash is handed to the **Lunch** app manager, who then updates the user's " +"account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:30 +msgid "" +"Money is automatically deducted from the user's paychecks, then the " +"**Lunch** app manager updates the account when paychecks are issued. This " +"requires :ref:`adding a salary attachment ` for " +"the user's payslip in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:33 +msgid "" +"Companies can sell \"lunch tickets\" at a set price (for example, one ticket" +" costs $5.00). Users can purchase tickets from a **Lunch** app manager, who " +"then updates the user's account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:39 +msgid "Cash Moves" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:41 +msgid "" +"To add funds to user accounts, each cash move must be individually logged. " +"To view all cash move records, or create a new cash move, navigate to " +":menuselection:`Lunch app --> Manager --> Cash Moves`. Doing so reveals the " +":guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:45 +msgid "" +"On the :guilabel:`Cash Moves` dashboard, all cash moves are presented in a " +"default list view, displaying each record's :guilabel:`Date`, " +":guilabel:`User`, :guilabel:`Description`, and :guilabel:`Amount`. The total" +" of all the cash moves is displayed at the bottom of the :guilabel:`Amount` " +"column." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The list view of all cash moves." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:54 +msgid "Add funds" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:56 +msgid "" +"To add funds to a lunch account, click the :guilabel:`New` button, located " +"in the top-left corner of the :guilabel:`Cash Moves` dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:59 +msgid "" +"A blank :guilabel:`Cash Moves` form loads. Enter the following information " +"on the form:" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:61 +msgid "" +":guilabel:`User`: select the user depositing cash into their account from " +"the drop-down menu. If the user is not in the database, they can be created " +"by typing their name in the :guilabel:`User` field, and clicking either " +":guilabel:`Create \"user\"` or :guilabel:`Create and edit...` to create the " +"user and edit the :guilabel:`Create User` form." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:65 +msgid "" +":guilabel:`Date`: using the calendar popover, select the date the " +"transaction occurred." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:66 +msgid ":guilabel:`Amount`: enter the amount being added to the lunch account." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:67 +msgid ":guilabel:`Description`: enter a brief description of the transaction." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "The cash move form filled out for a transaction of $40.00." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:73 +msgid "Control Accounts" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:75 +msgid "" +"An overview of every transaction in the **Lunch** app, including all cash " +"deposits and purchases, can be viewed on the main *Control Accounts* " +"dashboard. To access this dashboard, navigate to :menuselection:`Lunch app " +"--> Manager --> Control Accounts.`" +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:79 +msgid "" +"All transactions are grouped :guilabel:`By Employee`, and listed " +"alphabetically by the user's first name. At the end of the user's name, a " +"number appears. This indicates the number of individual records logged for " +"that user." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:83 +msgid "" +"The default view is to have all individual transactions hidden. To view all " +"transactions for a user, click the :icon:`fa-caret-right` " +":guilabel:`(triangle)` icon to the left of the desired name to expand that " +"specific group." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:87 +msgid "" +"Each record includes the :guilabel:`Date`, :guilabel:`User`, " +":guilabel:`Description`, and :guilabel:`Amount`." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:-1 +msgid "" +"The Control Accounts dashboard with two employee's transactions expanded." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:94 +msgid "" +"This list only displays the various transactions within the **Lunch** app, " +"and does **not** allow modifications to be made to any records listed." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:97 +msgid "" +"Cash moves can be modified, but **only** from the :ref:`Cash Moves " +"` dashboard, not from the :guilabel:`Control Accounts` " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/lunch/user-accounts.rst:100 +msgid "It is **not** possible to modify any product-related records." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:3 +msgid "Vendors" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:5 +msgid "" +"Before :doc:`products can be added ` to the **Lunch** app, the " +"restaurants that provide the food needs to be configured." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:8 +msgid "" +"To add a new vendor, first navigate to :menuselection:`Lunch app --> " +"Configuration --> Vendors`. Here, all currently configured vendors for the " +"**Lunch** app appear in a default Kanban view. To change to a list view, " +"click the :icon:`oi-view-list` :guilabel:`(List)` icon in the top-right " +"corner." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:14 +msgid "" +"No vendors are preconfigured in the **Lunch** app, so all vendors **must** " +"be added to the database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:17 +msgid "" +"A placeholder :guilabel:`Lunch Supplier` card appears on the " +":guilabel:`Vendors` dashboard, by default. Click on this card, and configure" +" the following fields on the vendor form:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:20 +msgid ":ref:`Vendor information `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:21 +msgid ":ref:`Availability `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:22 +msgid ":ref:`Orders `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:23 +msgid ":ref:`Extras `" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:25 +msgid "" +"After the first vendor is configured, add more vendors by clicking the " +":guilabel:`New` button in the top-left corner, and configure the new lunch " +"supplier form. Repeat for all needed vendors." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:31 +msgid "Vendor information" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:33 +msgid ":guilabel:`Vendor`: Enter a name for the vendor in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:34 +msgid "" +":guilabel:`Vendor` (beneath the line for vendor name): Using the drop-down " +"menu, select the corresponding vendor in the **Contacts** app. If the vendor" +" has not already been created, type in the vendor name, and click " +":guilabel:`Create \"new vendor name\"` to add them. Alternatively, click " +":guilabel:`Create and edit...` to create the vendor and edit the vendor " +"contact form. The vendor contact form allows for more details to be entered," +" such as contact information." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:41 +msgid "" +"If a selection is made to the drop-down :guilabel:`Vendor` field, the " +":guilabel:`Vendor` text field (above, for the vendor's name) updates with " +"the name of the vendor chosen from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:45 +msgid "" +"The list of vendors that is presented in the drop-down menu is pulled from " +"the **Contacts** application." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:48 +msgid ":guilabel:`Address`: Enter the vendor's address in the various fields." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:49 +msgid ":guilabel:`Email`: Enter the vendor's email in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:50 +msgid ":guilabel:`Phone`: Enter the vendor's phone number in this field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:51 +msgid "" +":guilabel:`Company`: If this vendor is only available to a specific company," +" select the company from the drop-down menu. If this field is left blank, " +"the vendor's items are available to **all** companies. This field **only** " +"appears in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The top portion of the vendor form filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:61 +msgid "Availability" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:63 +msgid "" +"The :guilabel:`AVAILABILITY` section presents a table with two rows. The " +"days of the week populate the top row, and the bottom row has checkboxes. " +"Tick the corresponding checkbox for each day of the week the vendor is " +"available." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:67 +msgid "By default, Monday through Friday are ticked." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The default view of the availability section, with Mon-Fri enabled." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:77 +msgid "" +"The :guilabel:`ORDERS` section of the vendor form details which locations " +"the vendor is available for, in addition to how and when orders are placed " +"and received." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:80 +msgid "" +":guilabel:`Delivery`: Using the drop-down menu, select :guilabel:`Delivery` " +"if the vendor delivers to the office, or select :guilabel:`No Delivery` if " +"orders must be picked up." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:82 +msgid "" +":guilabel:`Location`: Select which locations are able to order from this " +"vendor. Multiple locations can be selected. If this field is left blank, " +"**all** locations can order from the vendor." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:87 +msgid "" +"An `HQ Office` location is created by default when creating a database, and " +"is available to select from the list." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:90 +msgid "" +":guilabel:`Send Order By`: Click the radio button to select how orders are " +"sent to the vendor. The available options are :guilabel:`Phone` or " +":guilabel:`Email`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:92 +msgid "" +":guilabel:`Order Time`: This field **only** appears if :guilabel:`Email` is " +"selected in the :guilabel:`Send Order By` field. Enter the time that an " +"order must be emailed for it to be accepted. Enter the time in the following" +" format: `HH:MM`. Then select either :guilabel:`AM` or :guilabel:`PM` from " +"the drop-down menu, next to the time field." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:-1 +msgid "The orders section of a vendor form, with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:103 +msgid "Extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:105 +msgid "" +"When ordering an item in the **Lunch** app, optional extra items, sometimes " +"referred to as *add-ons*, can be shown. These can be configured in any " +"manner that suits the products being offered." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:109 +msgid "" +"By default, Odoo allows for three types of extra items, which can be thought" +" of as *categories*. By default, the first type (or *category*) of add-ons " +"is labeled `Extras`, the second is labeled `Beverages`, and the third is " +"labeled `Extra Label 3`." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:114 +msgid "" +"When configuring the extras, it is important to keep in mind that all the " +"extras configured appear for **every item** offered by the vendor. That " +"means that only items which apply to **all** products from the vendor should" +" be added." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:121 +msgid "Configure extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:123 +msgid "" +"Enter the following information for each of the three available extra " +"sections:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:125 +msgid "" +":guilabel:`Extra (#) Label`: Enter a name for the type of extra, such as " +"`Toppings`. This can be thought of as a *category*." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:127 +msgid "" +":guilabel:`Extra (#) Quantity`: Select how the extras are selected. The " +"options are:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:129 +msgid "" +":guilabel:`None or More`: Select this option if the user is not required to " +"make a selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:130 +msgid "" +":guilabel:`One or More`: Select this option to **require** the user to make " +"**at least one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:132 +msgid "" +":guilabel:`Only One`: Select this option to **require** the user to make " +"**only one** selection." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:135 +msgid "Add extras" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:137 +msgid "" +"After the labels and quantities have been configured for an extra category, " +"the individual extra items must be added for each category." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:140 +msgid "" +"Click :guilabel:`Add a line` at the bottom of the list that appears on the " +"right-hand side of the extra category. Enter the :guilabel:`Name` and " +":guilabel:`Price` for each item being added. The price can remain at `$0.00`" +" if there is no cost. This is common for items like disposable silverware or" +" condiments." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:146 +msgid "" +"For a pizzeria that only offers personal pizzas, see their extras configured" +" as follows:" +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:148 +msgid "" +"The first extra is configured for the various toppings they offer. The " +":guilabel:`Extra 1 Label` is set to `Toppings`, and the :guilabel:`Extra 1 " +"Quantity` is set to :guilabel:`None or More`. The various toppings are then " +"added, with their corresponding costs." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The first of the extras configured for pizza toppings." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:155 +msgid "" +"The pizzeria also offers a free beverage with any purchase. To set this up, " +"the :guilabel:`Extra 2 Label` is set to `Beverages`, and the " +":guilabel:`Extra 2 Quantity` is set to :guilabel:`Only One`. The various " +"beverage choices are added, and the cost for each remains zero." +msgstr "" + +#: ../../content/applications/hr/lunch/vendors.rst:0 +msgid "The second of the extras configured for a free beverage with purchase." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:5 +#: ../../content/applications/hr/payroll.rst:53 +#: ../../content/applications/hr/payroll/reporting.rst:31 +msgid "Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:7 +msgid "" +"Odoo *Payroll* is used to process work entries and create payslips for " +"employees. *Payroll* works in conjunction with other Odoo apps, such as " +"*Employees*, *Time Off*, *Attendances*, and *Planning*." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:10 +msgid "" +"The *Payroll* app helps ensure there are no issues or conflicts when " +"validating work entries. It also handles country-specific localizations to " +"ensure payslips follow local rules and taxes, and allows for salary " +"assignments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:17 +msgid "" +"Configure the *Payroll* app by navigating to :menuselection:`Payroll app -->" +" Configuration --> Settings`. The various settings for accounting, " +"localizations, time off, alerts, and payslips are specified here." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:24 +msgid "Accounting" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:26 +msgid "" +"The accounting section of the configuration menu relates to three options:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:28 +msgid "" +":guilabel:`Payroll Entries`: enable this option to post payroll slips in " +"accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:29 +msgid ":guilabel:`Payroll SEPA`: enable this option to create SEPA payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:30 +msgid "" +":guilabel:`Batch Account Move Lines`: enable this option to have a single " +"account move line created from all the accounting entries from the same " +"period. This disables the generation of single payments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:35 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2518 +#: ../../content/applications/hr/time_off.rst:5 +msgid "Time off" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:37 +msgid "" +":guilabel:`Deferred Time Off`: if time off is taken after payslips are " +"validated, the time off needs to be applied to the following pay period. " +"Select the person that will be notified for these specific time off " +"situations using the drop-down menu in the :guilabel:`Responsible` field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:42 +msgid "" +"An employee is paid on the 15th of the month and the last day of the month. " +"Payslips are typically processed a day before." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:45 +msgid "" +"If an employee's payslip is approved and processed on the 30th, but that " +"same employee takes an unexpected sick day on the 31st, the time off needs " +"to be logged." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:48 +msgid "" +"Since the employee is already paid for a regular work day on the 31st, to " +"keep the time off balances correct, the sick day is moved/applied to the 1st" +" of the next month (the next pay period)." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:55 +msgid "" +":guilabel:`Contract Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a contract expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:58 +msgid "" +":guilabel:`Work Permit Expiration Notice Period`: enter the number of " +":guilabel:`Days` before a work permit expires, and Odoo notifies the " +"responsible person about the upcoming expiration at that time." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:61 +msgid "" +":guilabel:`Payslip PDF Display`: enable this option to show the payslip's " +"PDF when the state is validated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:67 +#: ../../content/applications/hr/payroll/contracts.rst:3 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:77 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:52 +msgid "Contracts" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:69 +msgid "" +"In order for an employee to be paid, they **must** have an active contract " +"for a specific type of employment. Creating and viewing contract templates, " +"and creating and viewing employment types, is possible from this section of " +"the configuration header menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:76 +msgid "Templates" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:78 +msgid "" +"Contract templates are used when sending an offer to a candidate. The " +"contract template forms the basis of an offer, and can be modified for " +"specific candidates or employees, when necessary. If a contract template is " +"created or modified in the *Payroll* application, the changes are also " +"reflected in the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:84 +msgid "" +"To access contract templates, the *Salary Configurator* " +"(`hr_contract_salary`) module **must** be :ref:`installed " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:87 +msgid "" +"To view all the current contract templates in the database, navigate to " +":menuselection:`Payroll app --> Configuration --> Contracts: Templates`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:90 +msgid "" +"On the :guilabel:`Contract Templates` page, all current contract templates " +"appear in a list view. To view the details of a contract template, click " +"anywhere on the line to open the contract form. The contract template can be" +" modified from this form. Proceed to make any desired changes to the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:95 +msgid "" +"To create a new contract template, click the :guilabel:`New` button. Then, " +"enter the following information on the blank contract template form that " +"appears:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:98 +msgid "" +":guilabel:`Contract Reference`: enter a brief description for the template. " +"This should be clear and easily understood, as this name appears in the " +"*Recruitment* application, as well." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:100 +msgid "" +":guilabel:`Working Schedule`: select the desired working schedule the " +"contract applies to from the drop-down menu. If a new working schedule is " +"needed, create a :ref:`new working schedule `." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:103 +msgid "" +":guilabel:`Work Entry Source`: select how the work entries are generated. " +"Choices are either:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:105 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:106 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"attendance, as they are logged in the *Attendances* application. Refer to " +"the :ref:`Attendances ` documentation for information " +"on checking in and out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:109 +msgid "" +":guilabel:`Planning`: work entries are generated based on the employee's " +"planning in the *Planning* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:112 +msgid "" +":guilabel:`Salary Structure Type`: select the :ref:`salary structure type " +"` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:114 +msgid "" +":guilabel:`Department`: select the department the contract template applies " +"to from the drop-down menu. If blank, the template applies to all " +"departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:116 +msgid "" +":guilabel:`Job Position`: select the :ref:`job position ` the contract template applies to from the drop-down menu. If " +"blank, the template applies to all job positions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:118 +msgid ":guilabel:`Wage on Payroll`: enter the monthly wage in the field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:119 +msgid "" +":guilabel:`Contract Type`: select the type of contract from the drop-down " +"menu. This list is the same as the :ref:`Employment Types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:121 +msgid "" +":guilabel:`HR Responsible`: select the employee responsible for validating " +"contracts, using this template, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:123 +msgid "" +":guilabel:`New Contract Document Template`: select a default document that a" +" new employee has to sign to accept an offer." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:125 +msgid "" +":guilabel:`Contract Update Document Template`: select a default document " +"that a current employee has to sign to update their contract." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new contract template form, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:133 +msgid "Salary information tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:135 +msgid "" +":guilabel:`Wage Type`: select either :guilabel:`Fixed Wage` or " +":guilabel:`Hourly Wage` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:137 +msgid "" +":guilabel:`Schedule Pay`: using the drop-down menu, select how often the " +"employee is paid. Options include :guilabel:`Annually`, :guilabel:`Semi-" +"annually`, :guilabel:`Quarterly`, :guilabel:`Bi-monthly`, " +":guilabel:`Monthly`, :guilabel:`Semi-monthly`, :guilabel:`Bi-weekly`, " +":guilabel:`Weekly`, or :guilabel:`Daily`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:141 +msgid "" +":guilabel:`Wage`: enter the gross wage. The time period presented in this " +"field is based on what is selected for the :guilabel:`Scheduled Pay` field. " +"It is recommended to populate the :guilabel:`Yearly Cost (Real)` field " +"*first*, since that entry updates this field automatically." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:144 +msgid "" +":guilabel:`Yearly Cost (Real)`: enter the total yearly cost the employee " +"costs the employer. When this value is entered, the :guilabel:`Monthly Cost " +"(Real)` is automatically updated." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:146 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field is **not** editable. The value " +"is automatically populated after the :guilabel:`Yearly Cost (Real)` is " +"entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:150 +msgid "" +"The :guilabel:`Schedule Pay`, :guilabel:`Wage`, and :guilabel:`Yearly Cost " +"(Real)` fields are all linked. If any of these fields are updated, the other" +" two fields automatically update to reflect the change. It is best practice " +"to check these three fields if any modifications have been made, to ensure " +"they are accurate." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The salary information tab, with the fields filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:160 +msgid "Pre-tax benefits and post-tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:162 +msgid "" +"Depending on the localization settings set for the company, the entries " +"presented in this section either vary, or may not appear at all." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:165 +msgid "" +"For example, some entries may pertain to retirement accounts, health " +"insurance benefits, and commuter benefits." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:168 +msgid "" +"Enter the monetary amounts or percentages to specify how much of the " +"employee's salary goes to the various benefits and/or deductions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:174 +msgid "Employment types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:176 +msgid "" +"To view all the pre-configured employment types, navigate to " +":menuselection:`Payroll application --> Configuration --> Contracts: " +"Employment Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:179 +msgid "" +"The employment types are presented in a list view on the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:181 +msgid "" +"The default employment types are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Interim`, " +":guilabel:`Full-Time`, :guilabel:`Part-Time`, and :guilabel:`Permanent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:184 +msgid "" +"To make a new employment type, click the :guilabel:`New` button in the " +"upper-left corner, and a blank line appears at the bottom of the " +":guilabel:`Employment Types` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:187 +msgid "" +"On this new blank line, enter the name of the employment type in the " +":guilabel:`Name` column. If the employment type is country-specific, select " +"the country using the drop-down menu in the :guilabel:`Country` column. If a" +" country is selected, then the employment type is *only* applicable for that" +" specific country." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:192 +msgid "" +"To rearrange the order of the employment types, click the :guilabel:`six " +"small gray boxes` icon to the left of the employment type :guilabel:`Name`, " +"and drag the line to the desired position on the list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "The employment types in the database by default, in a list view." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:203 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:29 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2766 +#: ../../content/applications/hr/payroll/work_entries.rst:3 +msgid "Work entries" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:205 +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:210 +msgid ":doc:`Manage work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:213 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:786 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2776 +msgid "Work entry types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:215 +msgid "" +"When creating a work entry in the *Payroll* application, or when an employee" +" enters new time off types in *Time Off* 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:220 +msgid "" +"To view the current work entry types available, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Work " +"Entry Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:223 +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:231 +msgid "New work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:233 +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:237 +#: ../../content/applications/hr/payroll.rst:665 +#: ../../content/applications/hr/payroll/contracts.rst:40 +msgid "General information section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:239 +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:241 +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:244 +msgid "" +":guilabel:`External Code`: this code is used for exporting data to a third-" +"party payroll service. Check with the third-party being used to determine " +"the :guilabel:`External Code` to enter for the new work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:247 +msgid ":guilabel:`Color`: select a color for the particular work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:250 +msgid "Display in payslip section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:252 +msgid "" +":guilabel:`Rounding`: the rounding method selected determines how quantities" +" on timesheet entries are displayed on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:255 +msgid ":guilabel:`No Rounding`: entry is not modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:256 +msgid ":guilabel:`Half Day`: entry is rounded to the closest half day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:257 +msgid ":guilabel:`Day`: entry is rounded to the closest full day amount." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:260 +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 work entry, 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:266 +msgid "Unpaid section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:268 +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 is logged on a payslip, " +"but no compensation given would be for unpaid internships, unpaid training, " +"or volunteer work." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:274 +msgid "Valid for advantages section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:276 +msgid "" +":guilabel:`Meal Voucher`: if the work entry should count towards a meal " +"voucher, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:277 +msgid "" +":guilabel:`Representation Fees`: if the work entry should count towards " +"representation fees, check the box." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:279 +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:283 +msgid "Time off options section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:285 +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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:288 +msgid "" +"If :guilabel:`Time Off` is checked, a :guilabel:`Time Off Type` field " +"appears. This field has a drop-down menu to select the specific types of " +"time off, such as `Paid Time Off`, `Sick Time Off`, or `Extra Hours`, for " +"example." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:292 +msgid "" +"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:296 +msgid "Reporting section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:298 +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:308 +msgid "Working schedules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:310 +msgid "" +"To view the currently configured working schedules, go to " +":menuselection:`Payroll app --> Configuration --> Work Entries --> Working " +"Schedules`. The working schedules that are available for an employee's " +"contracts are found in this list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:314 +msgid "" +"Working schedules are company-specific. Each company **must** identify each " +"type of working schedule they use. If the database is created for only one " +"company, the company column is not available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:318 +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:321 +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:331 +msgid "New working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:333 +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:336 +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:340 +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:346 +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:349 +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:363 +msgid "Structure types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:365 +msgid "" +"In Odoo, structure types are used to identify group of people referring to " +"the same payroll rules. A structure type contains specific options and a " +"subset of structures that will be used according the situation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:369 +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:375 +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:381 +msgid "" +"The different :guilabel:`Structure Types` can be seen by navigating to " +":menuselection:`Payroll app --> Configuration --> Salary: Structure Types`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:384 +msgid "" +"Two default structure types are configured in Odoo: :guilabel:`Employee` and" +" :guilabel:`Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:386 +msgid "" +"Typically, :guilabel:`Employee` is used for salaried employees, which is why" +" the wage type is :guilabel:`Monthly Fixed Wage`, and :guilabel:`Worker` is " +"typically used for employees paid by the hour, so the wage type is " +":guilabel:`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:397 +msgid "New structure type" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:399 +msgid "" +"To make a new structure type, click the :guilabel:`New` button, and a blank " +"structure type form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:402 +msgid "" +"Proceed to enter information in the fields. Most fields are pre-populated, " +"but all the fields can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:405 +msgid "" +":guilabel:`Structure Type`: enter the name for the new structure type, such " +"as `Employee` or `Worker`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:407 +msgid "" +":guilabel:`Country`: select the country that the new structure type applies " +"to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:409 +msgid "" +":guilabel:`Wage Type`: select what type of wage the new structure type uses," +" either :guilabel:`Fixed Wage` or :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:412 +msgid "" +"If the type is to be used for salaried employees, who receive the same wage " +"every pay period, select :guilabel:`Fixed Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:415 +msgid "" +"If the type is 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:417 +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 specific type of structure is paid out." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:421 +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:426 +msgid "" +":guilabel:`Regular Pay Structure`: type in the name for the regular pay " +"structure. It will be used as the default option when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:428 +msgid "" +":guilabel:`Default Work Entry Type`: For employees whose contracts is " +"referred under this structure type, the main work entry type used for all " +"period of work is defined here. It will commonly be set as **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`, " +":guilabel:`Out Of Contract`, :guilabel:`Extra Hours`, and :guilabel:`Long " +"Term Time Off`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:435 +msgid "" +"To view all the options for the :guilabel:`Default Work Entry Type`, click " +"the :guilabel:`Search More..` button at the bottom of the drop-down list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:438 +msgid "" +"Depending on the localization settings, this list may contain more options " +"in addition to the default options." +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:448 +msgid "New default working hours" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:450 +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 pops " +"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 completed, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:456 +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:458 +msgid "" +":guilabel:`Company`: select the company that can use these new default " +"working hours from the drop-down menu. Blank field means it's available for " +"all companies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:460 +msgid "" +":guilabel:`Average Hour Per Day`: the average hours per day field is auto-" +"populated, based on the working hours configured in the :guilabel:`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:464 +msgid "" +":guilabel:`Timezone`: select the time zone to be used for the new default " +"working hours from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:466 +msgid "" +":guilabel:`Company Full Time`: enter the number of hours per week an " +"employee would need to work 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:470 +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 :guilabel:`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:474 +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 " +":guilabel:`Working Hours` tab is pre-populated with a default 40-hour week, " +"with each day divided into three timed sections." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:478 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:481 +msgid "" +"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:484 +msgid "" +"Keep in mind, working hours are company-specific, and cannot be shared " +"between companies. Each company needs to have their own working hours set." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:488 +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 changes the " +":guilabel:`Working Hours` tab to display two weeks of working times that can" +" be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:494 +msgid "Structures" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:496 +msgid "" +"*Salary structures* are the different situations an employee could be paid " +"within a specific *structure*, and are specifically defined by various " +"rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:499 +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:503 +msgid "" +"To view all the various structures for each structure type, go to " +":menuselection:`Payroll app --> Configuration --> Salary --> Structures`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:506 +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:513 +msgid "" +"Click on a structure to view its :guilabel:`Salary Rules`. These rules " +"define how the payslip will be computed 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:521 +#: ../../content/applications/hr/time_off.rst:300 +msgid "Rules" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:523 +msgid "" +"Each structure has a set of salary rules used to compute the various amounts" +" considered in the pay. These rules are configured by the localization and " +"affect the computation of the salaries. Modification or creation of rules " +"should only be done when necessary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:527 +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:530 +msgid "" +"To make a new rule, click :guilabel:`New`. A new rule form appears. Enter " +"the following information in the fields." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:534 +msgid "Top section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:536 +msgid "" +":guilabel:`Rule Name`: enter a name for the rule. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:537 +msgid "" +":guilabel:`Category`: select a category the rule applies to from the drop-" +"down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:539 +msgid "" +":guilabel:`Code`: enter a code to be used for this new rule. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:540 +msgid "" +":guilabel:`Sequence`: enter a number indicating when this rule is calculated" +" in the sequence of all other rules." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:542 +msgid "" +":guilabel:`Salary Structure`: select a salary structure the rule applies to " +"from the drop-down menu, or enter a new one. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:544 +msgid "" +":guilabel:`Active`: enable this toggle, so the rule is available for use. " +"Disable the toggle to continue to show it on the payslip, but skip the " +"computation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:546 +msgid "" +":guilabel:`Appears on payslip`: tick the checkbox to have the rule appear on" +" employee printed payslip." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:548 +msgid "" +":guilabel:`View on Employer Cost Dashboard`: tick the checkbox to have the " +"rule appear on the :guilabel:`Employer Cost` report, located on the " +"*Payroll* app dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:550 +msgid "" +":guilabel:`View on Payroll Reporting`: tick the checkbox to have the rule " +"appear on payroll reports." +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:558 +msgid "General tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:561 +msgid "Conditions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:563 +msgid "" +":guilabel:`Condition Based on`: 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). " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:569 +msgid "Computation" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:571 +msgid "" +":guilabel:`Amount Type`: 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. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:577 +msgid "Company contribution" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:579 +msgid "" +":guilabel:`Partner`: if another company financially contributes to this " +"rule, select the company from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:583 +#: ../../content/applications/hr/payroll.rst:749 +msgid "Description tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:585 +msgid "" +"Provide any additional information in this tab to help clarify the rule. " +"This tab only appears in the rule form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:589 +msgid "Accounting tab" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:591 +msgid "" +":guilabel:`Debit Account`: select the debit account from the drop-down menu " +"the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:592 +msgid "" +":guilabel:`Credit Account`: select the credit account from the drop-down " +"menu the rule affects." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:593 +msgid "" +":guilabel:`Not computed in net accountability`: If checked, the amount of " +"the rule will be show independantly from the Net Salary, to allow a better " +"reporting in Accounting." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:597 +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:730 +msgid "Other input types" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:599 +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 navigating to :menuselection:`Payroll app " +"--> 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:608 +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:613 +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 "A new Input Type form filled in." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:624 +#: ../../content/applications/hr/recruitment.rst:94 +msgid "Salary package configurator" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:626 +msgid "" +"The various options under the :guilabel:`Salary Package Configurator` " +"section of the :menuselection:`Payroll app --> Configuration --> Salary " +"Package Configurator` menu all affect an employee's potential salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:630 +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:636 +msgid "Benefits" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:638 +msgid "" +"When offering potential employees a position, there can be certain 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:642 +msgid "" +"To view the benefits, go to :menuselection:`Payroll app --> Configuration " +"--> Salary Package Configurator: Benefits`. Benefits are grouped by " +":guilabel:`Structure type`, and the benefit 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 benefits available for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:651 +msgid "" +"A company has two structure types, one labeled :guilabel:`Employee`, and " +"another labeled :guilabel:`Intern`. The :guilabel:`Employee` structure type " +"contains the benefit of using a company car, while the :guilabel:`Intern` " +"structure type has a meal voucher benefit available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:655 +msgid "" +"A person hired under the :guilabel:`Employee` structure type can use the " +"company car benefit, but cannot have meal vouchers. A person hired under the" +" :guilabel:`Intern` structure type would have meal voucher benefits " +"available to them, not the use of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:659 +msgid "" +"To make a new benefit, click the :guilabel:`New` button, and enter the " +"information in the fields on the blank benefits form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:662 +msgid "The various fields for creating a benefit are as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:667 +msgid "" +":guilabel:`Contract Related Field`: select from the drop-down menu a field " +"from the contract. The choosen value from the employee will be recorded to " +"that field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:669 +msgid "" +":guilabel:`Benefits`: enter the name for the benefit. This field is " +"required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:670 +msgid "" +":guilabel:`Benefit Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:674 +msgid "" +":guilabel:`Cost Field`: select from the drop-down menu a field from the " +"contract. The field will define the cost of the benefit and by extention the" +" impact on the salary, :guilabel:`Wage`, :guilabel:`Wage with Holidays`, and" +" :guilabel:`Work time rate`. Depending on the localization settings, " +"additional options are available." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:678 +msgid "" +":guilabel:`Related Type`: select from the drop-down menu what type of " +"benefit it is. Select from :guilabel:`Monthly Benefit in Kind`, " +":guilabel:`Monthly Benefit in Net`, :guilabel:`Monthly Benefit in Cash`, " +":guilabel:`Yearly Benefits in Cash`, or :guilabel:`Non Financial Benefits`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:682 +msgid "" +":guilabel:`Impacts Net Salary`: tick the checkbox if the benefit should " +"impact the employee's net salary." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:684 +msgid "" +":guilabel:`Requested Documents`: select any document that is required to be " +"submitted for this benefit, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:686 +msgid "" +":guilabel:`Mandatory Benefits`: using the drop-down menu, select the benefit" +" that is required in order for this specific benefit to be offered to the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:689 +msgid "" +"For example, a benefit for car insurance would populate `Company Car` in " +"this field. This would allow the car insurance benefit to **only** be " +"displayed if the employee has selected/enabled the benefit of a company car." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:692 +msgid "" +":guilabel:`Salary Structure Type`: select from the drop-down menu which " +"salary structure type this benefit applies to. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:694 +msgid "" +":guilabel:`Unit of Measure`: select the metric that the benefit is granted, " +"using the drop-down menu. The options are :guilabel:`Days`, " +":guilabel:`Percent`, or :guilabel:`Currency`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A new benefit form filled out for an internet subscription." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:702 +msgid "Display section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:704 +msgid "" +":guilabel:`Show Name`: tick the checkbox to have the benefit name appear in " +"the salary package configurator." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:706 +msgid "" +":guilabel:`Display Type`: select from the drop-down menu how this benefit is" +" displayed. The options are :guilabel:`Always Selected`, " +":guilabel:`Dropdown`, :guilabel:`Dropdown Group`, :guilabel:`Slider`, " +":guilabel:`Radio Buttons`, :guilabel:`Manual Input`, or :guilabel:`Text`. " +"This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:711 +msgid "" +"Depending on the selection made, additional configurations need to be made. " +"For example, if :guilabel:`Radio Buttons` is selected, the individual radio " +"buttons must be entered." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:713 +msgid "" +":guilabel:`Icon`: an icon from the `Font Awesome 4 library " +"`_ can be visible for this benefit. Enter" +" the text code for the icon in this field. For example, to display a " +"suitcase icon, the code `fa fa-suitcase` is entered on this line." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:716 +msgid "" +":guilabel:`Hide Description`: tick the checkbox to hide the benefit " +"description if the benefit is not selected by the employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:718 +msgid "" +":guilabel:`Folded`: if the benefit should be folded, or hidden, because it " +"is dependant on another benefit selection, tick the checkbox. The following " +"fields appear when this is active:" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:721 +msgid "" +":guilabel:`Fold Label`: enter a name for the folded section of the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:722 +msgid "" +":guilabel:`Fold Res Field`: select the contract field this benefit is tied " +"to using the drop-down menu. If this field is selected on the contract, then" +" this benefit becomes visible." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:726 +msgid "Activity section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:728 +msgid "" +":guilabel:`Activity Type`: from the drop-down menu, select the activity type" +" that is automatically created when this benefit is selected by the " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:730 +msgid "" +":guilabel:`Activity Creation`: select when the activity is created, either " +"when the :guilabel:`Employee signs his contract`, or when the " +":guilabel:`Contract is countersigned`. Click the radio button next to the " +"desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:733 +msgid "" +":guilabel:`Activity Creation Type`: select the parameters for when the " +"activity is created, either :guilabel:`When the benefit is set` or " +":guilabel:`When the benefit is modified`. Click the radio button next to the" +" desired selection." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:736 +msgid "" +":guilabel:`Assigned to`: select the user the activity is automatically " +"assigned to, using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:740 +#: ../../content/applications/hr/payroll/contracts.rst:133 +msgid "Sign section" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:742 +msgid "" +":guilabel:`Template to Sign`: if the employee is required to sign a document" +" when selecting this benefit, select the document template from the drop-" +"down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:745 +msgid "" +"For example, a benefit regarding the use of a company car may require the " +"employee to sign a document acknowledging the company's car policies." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:751 +msgid "" +"Provide any additional information in this tab to help clarify the benefit." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:754 +msgid "Personal info" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:756 +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:760 +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:764 +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:768 +msgid "An employee card can be thought of as an employee personal file." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:770 +msgid "" +"The :guilabel:`Personal Info` section lists all of the fields that are " +"available to enter on the employee's card. To access this section, go to " +":menuselection:`Payroll app --> Configuration --> Salary Package " +"Configurator: Personal Info`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"A list of all the personal information that appears on the employee card to " +"enter." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:778 +msgid "" +"To edit a personal info entry, select an entry from the list on the " +":guilabel:`Personal Info` page, and modify the personal info on the form " +"that appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:781 +msgid "To create a new personal info entry, click the :guilabel:`New` button." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:783 +msgid "" +"The required fields, aside from entering the :guilabel:`Information` name, " +"are :guilabel:`Related Model`, :guilabel:`Related Field`, and " +":guilabel:`Category`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:786 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:790 +msgid "" +"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 " +"stored in the backend. 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:795 +msgid "" +"The two most important fields on the personal info form are :guilabel:`Is " +"Required` and :guilabel:`Display Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:798 +msgid "" +"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, like 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:810 +msgid "" +"The resumé section, housed within the salary package configurator section of" +" the settings menu, is how salary information rules are configured when " +"offering a position to potential employees." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:813 +msgid "" +"When an offer is sent to a prospective employee, the values for the offer " +"are computed from these settings, and appear on the offer page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:816 +msgid "" +"To configure this section, navigate to :menuselection:`Payroll app --> " +"Configuration --> Salary Package Configurator: Resumé`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:819 +msgid "" +"By default, there are three :guilabel:`Salary Structure Types` pre-" +"configured in Odoo: :guilabel:`Worker`, :guilabel:`Employee`, and " +":guilabel:`None`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:822 +msgid "" +"Each :guilabel:`Salary Structure Type` has several rules configured. These " +"affect how an offer is calculated using that particular :guilabel:`Salary " +"Structure Type`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:825 +msgid "" +"To create a new rule, click the :guilabel:`New` button, and a blank " +":guilabel:`Contract Salary Resumé` form loads." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:830 +msgid ":guilabel:`Information`: type in a name for this field." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:831 +msgid "" +":guilabel:`Category`: select the category this value is housed under, using " +"the drop-down menu. The default options are :guilabel:`Monthly Salary`, " +":guilabel:`Monthly Benefits`, :guilabel:`Yearly Benefits`, and " +":guilabel:`Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:835 +msgid "New categories can be made if needed." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:837 +msgid "" +"Click the :guilabel:`New` button, then enter the name for the new category " +"in the :guilabel:`Name` field. Next, select the :guilabel:`Periodicity` from" +" the drop-down menu, either :guilabel:`Monthly` or :guilabel:`Yearly`. Last," +" enter a number for the sequence. This corresponds to where this rule " +"appears in the :guilabel:`Salary Structure Type` rule list." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:842 +msgid "Finally, click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:843 +msgid "" +":guilabel:`Impacts Monthly Total`: tick the checkbox if this value is added " +"in the monthly total calculation." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:845 +msgid "" +":guilabel:`Unit of Measure`: select what kind of value this rule is, either " +":guilabel:`Currency`, :guilabel:`Days`, or :guilabel:`Percent`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:848 +msgid "" +":guilabel:`Currency` is for a set monetary value, :guilabel:`Days` is for " +"compensation in the form of time off, and :guilabel:`Percent` is for a " +"monetary value awarded that is based upon another metric, such as " +"commissions." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:851 +msgid "" +":guilabel:`Salary Structure Type`: select which :guilabel:`Salary Structure " +"Type` this rule is nested under, from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:853 +msgid "" +":guilabel:`Value Type`: select how the value is computed, using the drop-" +"down menu. The default options are :guilabel:`Fixed Value`, " +":guilabel:`Contract Value`, :guilabel:`Payslip Value`, :guilabel:`Sum of " +"Benefits Values`, and :guilabel:`Monthly Total`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:856 +msgid "" +":guilabel:`Code`: select the code this rule applies to from the drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "" +"The net wage rule form filled out, with all the information for net pay." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:863 +msgid "Jobs" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:865 +msgid "" +"Since the *Payroll* application is responsible for paying employees for " +"specific job positions, the complete list of job positions can be found in " +"both the *Payroll* and *Recruitment* applications." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:871 +#: ../../content/applications/hr/recruitment/new_job.rst:3 +msgid "Job positions" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:873 +msgid "" +"The job positions listed in the *Payroll* application are identical to the " +"job positions listed in the *Recruitment* application. If a new job position" +" is added in the *Recruitment* application, it is also visible in the " +"*Payroll* application, and vice versa." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:877 +msgid "" +"To view the job positions, navigate to :menuselection:`Payroll app --> " +"Configuration --> Jobs: Job Positions`." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:880 +msgid "" +"A list of all the job positions appear, along with the corresponding " +"department, on the :guilabel:`Job Position` page." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:-1 +msgid "A list of all the job positions and corresponding departments." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:887 +msgid "" +"To create a new job description, click the :guilabel:`New` button and a job " +"form appears." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:889 +msgid "" +"Enter the information on the form for the new position. The information is " +"identical as to the information entered when creating a new job position in " +"the *Recruitment* application." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:892 +msgid "" +"Refer to the :doc:`../hr/recruitment/new_job` documentation for more details" +" on how to fill out this form." +msgstr "" + +#: ../../content/applications/hr/payroll.rst:896 +msgid ":doc:`payroll/contracts`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:897 +msgid ":doc:`payroll/work_entries`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:898 +msgid ":doc:`payroll/salary_attachments`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:899 +msgid ":doc:`payroll/payslips`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:900 +msgid ":doc:`payroll/reporting`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:901 +msgid ":doc:`payroll/work_entry_analysis`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:902 +msgid ":doc:`payroll/salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll.rst:903 +msgid ":doc:`payroll/payroll_localizations`" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:5 +msgid "" +"Every employee in Odoo is required to have a running contract in order to be" +" paid. A contract outlines the terms of an employee's position, their " +"compensation, 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 to send and sign contracts. Please refer to the " +":doc:`../../productivity/documents` and :doc:`../../productivity/sign` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:15 +msgid "" +"To view the employee contracts, go to the :menuselection:`Payroll app --> " +"Contracts --> Contracts` from the top menu. All employee contracts, and " +"their current contract status, are displayed in a list view, by default. The" +" list view displays running contracts, contracts that require action, " +"expired contracts, and cancelled contracts." +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." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:30 +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 " +":guilabel:`Contracts` dashboard. A contract form appears where the " +"information can be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:35 +msgid "New contract form" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:42 +msgid "" +":guilabel:`Contact Reference`: type in the name or title for the contract, " +"such as `John Smith Contract`. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:44 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee that the" +" contract applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:45 +msgid "" +":guilabel:`Contract Start Date`: the date the contract starts. To choose a " +"date, click the drop-down menu, navigate to the correct month and year with " +"the :guilabel:`< > (arrow)` icons, then click on the desired date. This " +"field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:48 +msgid "" +":guilabel:`Contract End Date`: if the contract has a specific end date, " +"click the drop-down menu, navigate to the correct month and year with the " +":guilabel:`< > (arrow)` icons, then click on the desired date." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:51 +msgid "" +":guilabel:`Working Schedule`: select one of the working schedules from the " +"drop-down menu. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:55 +msgid "" +"The :guilabel:`Working Schedule` drop-down menu displays all the working " +"schedules for the selected company. To modify or add to this list, go to " +":menuselection:`Payroll app --> Configuration --> Working Schedules`. Click " +":guilabel:`New`, and create a new working schedule, or click on an existing " +"working schedule and make edits." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:60 +msgid "" +":guilabel:`Work Entry Source`: select how the :doc:`work entries " +"` are generated. This field is **required**. Click the radio " +"button next to the desired selection. The options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:63 +msgid "" +":guilabel:`Working Schedule`: work entries are generated based on the " +"selected :guilabel:`Working Schedule`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:65 +msgid "" +":guilabel:`Attendances`: work entries are generated based on the employee's " +"check-in records in the *Attendances* application. (This requires the " +"*Attendances* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:67 +msgid "" +":guilabel:`Planning`: work entries are generated based on the planned " +"schedule for the employee from the *Planning* application. (This requires " +"the *Planning* application)." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:70 +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 :ref:`new salary structure " +"type ` can be created, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:73 +msgid "" +":guilabel:`Department`: select the department the contract applies to from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:74 +msgid "" +":guilabel:`Job Position`: select the specific job position the contract " +"applies to from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:78 +msgid "" +"If the selected :guilabel:`Job Position` has a contract template linked to " +"it with a specific :guilabel:`Salary Structure Type`, the :guilabel:`Salary " +"Structure Type` changes to the one associated with that :guilabel:`Job " +"Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:82 +msgid ":guilabel:`Wage on Payroll`: enter the employee's monthly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:83 +msgid "" +":guilabel:`Contract Type`: choose either :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, or " +":guilabel:`Part-Time` from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"New contract form to be filled in when creating a new contract, with required fields\n" +"outlined in red." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:92 +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 app --> Configuration --> Working Times`, and " +"either :guilabel:`Create` a new working time, or click on an existing " +"working time, then edit it by clicking :guilabel:`Edit`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:97 +msgid "" +":guilabel:`Yearly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total yearly cost for the employer. This field can be " +"modified. However, if this is modified, the :guilabel:`Wage` field updates, " +"accordingly. Ensure both the :guilabel:`Wage` and :guilabel:`Yearly Cost " +"(Real)` are correct if this field is modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:102 +msgid "" +":guilabel:`Monthly Cost (Real)`: this field automatically updates after the " +":guilabel:`Schedule Pay` and :guilabel:`Wage` fields are entered. This " +"amount is the total monthly cost for the employer. This field **cannot** be " +"modified, and is calculated based on the :guilabel:`Yearly Cost (Real)`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:0 +msgid "Optional tabs for a new contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:112 +msgid "Contract Details tab" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:114 +msgid "" +"The :guilabel:`Contract Details` tab allows for the addition and editing of " +"a contract, along with specifying which template to use when a new contract " +"is created. These fields **must** be populated in order to create a new " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:119 +msgid "" +"To access the various contract template fields in the :guilabel:`Contract " +"Details` tab, the *Salary Configurator* (`hr_contract_salary`) module " +"**must** be :ref:`installed `." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:123 +msgid "" +"When the *Salary Configurator* module is installed, the *Salary Configurator" +" - Holidays* and *Salary Configurator - Payroll* modules install, as well." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:126 +msgid "" +"Once the modules are installed, the database reverts to the main dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:128 +msgid "" +":guilabel:`Contract Template`: select a pre-existing contract template from " +"the drop-down menu. Contract templates are typically created through the " +"configuration menu, and stored in the *Documents* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:135 +msgid "" +":guilabel:`HR Responsible`: select the person who is responsible for " +"validating the contract from the drop-down menu. This field is required." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:137 +msgid "" +":guilabel:`New Contract Document Template`: select a contract from the drop-" +"down menu to be modified for this new employee contract. These documents are" +" stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:139 +msgid "" +":guilabel:`Contract Update Document Template`: select a contract from the " +"drop-down menu, if the employee has an existing contract that requires " +"updating. These documents are stored in the *Sign* application." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:144 +msgid "" +"The :guilabel:`HR Responsible`, :guilabel:`New Contract Document Template`, " +"and :guilabel:`Contract Update Document Template` fields are only visible if" +" the *Sign* application is installed, along with the `hr_contract_salary` " +"and `hr_contract_salary_payroll` :doc:`modules " +"<../../general/apps_modules>`. The *Sign* application is where the contract " +"templates are stored. This application is required for an employee to sign " +"any contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:151 +msgid "Accounting section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:153 +msgid "" +":guilabel:`Analytic Account`: select the account the contract affects from " +"the drop-down menu. It is recommended to check with the accounting " +"department to ensure the correct account is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:157 +msgid "Part Time section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:159 +msgid "" +":guilabel:`Part Time`: tick this box if the employee is working part-time. " +"When active, additional fields appear:" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:162 +msgid "" +":guilabel:`% (Percentage)`: enter the percent of time the employee works as " +"compared to a full-time employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:164 +msgid "" +":guilabel:`Standard Calendar`: select the working hours that a typical full-" +"time worker uses from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:166 +msgid "" +":guilabel:`Part Time Work Entry Type`: select the work entry type that " +"generates the balance of a full-time working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:170 +msgid "" +"If a full-time employee works 40 hours a week, and the employee works 20, " +"enter `50` in the :guilabel:`% (Percentage)` field (50% of 40 hours = 20 " +"hours). The employee generates twenty (20) hours of work entries under the " +"work entry type `part-time`, and another twenty (20) hours of work entries " +"under the work entry type `generic time off`, for a total of forty (40) " +"hours worth of work entries." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:177 +msgid "Notes section" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:179 +msgid "" +":guilabel:`Notes`: a text field where any notes for the employee contract " +"are entered for future reference." +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:187 +msgid "Modify a contract template" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:189 +msgid "" +"Click the :icon:`fa-external-link` :guilabel:`(external Link)` icon at the " +"end of either the :guilabel:`New Contract Document Template` or " +":guilabel:`Contract Update Document Template` to open the corresponding " +"contract template, and proceed to make any desired changes." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:193 +msgid "" +"Click the :guilabel:`Upload your file` button next to the corresponding " +"document, navigate to the file, then click :guilabel:`Open` to select the " +"document and add it to the tab." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:197 +msgid "Modifying document templates" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:199 +msgid "" +"Contracts templates can be modified at any point when changes are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:201 +msgid ":guilabel:`Tags`: select any tags associated with the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:202 +msgid "" +":guilabel:`Signed Document Workspace`: this is where the signatures are " +"stored. Choose a pre-configured workspace, or create a new one. To create a " +"new :guilabel:`Signed Document Workspace`, type in the name of the " +"workspace, then click either :guilabel:`Create` to add the new workspace, or" +" :guilabel:`Create and Edit` to add the workspace and modify the workspace " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:206 +msgid "" +":guilabel:`Signed Document Tags`: select or create any tags that are only " +"associated with the signed contract, as opposed to the original unsigned " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:208 +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, it takes them to the newly-updated contract specifically written " +"for them." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:211 +msgid "" +":guilabel:`Who can Sign`: select either :guilabel:`All Users` or " +":guilabel:`On Invitation`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:213 +msgid "" +":guilabel:`All Users`: any user in the organization can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:214 +msgid "" +":guilabel:`On Invitation`: only users selected in this field can sign the " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:216 +msgid "" +":guilabel:`Invited Users`: select the person (or people) that can sign the " +"document." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:217 +msgid "" +":guilabel:`Document`: the attached document can be replaced by clicking the " +":icon:`fa-pencil` :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 :icon:`fa-trash-o` :guilabel:`(trash can)` " +"icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:222 +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:227 +msgid "Personal documents" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:229 +msgid "" +"This tab **only** appears after an :guilabel:`Employee` is selected, and " +"houses any documents that are linked to the employee on their employee " +"record. Documents cannot be added to this tab, this tab **only** shows " +"documents that are already uploaded and associated with the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:233 +msgid "" +"The available documents in this tab can be downloaded. Click the :icon:`fa-" +"download` :guilabel:`(download)` icon next to the document to download it." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:237 +msgid "Send the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:239 +msgid "Click on the following button 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:245 +msgid "" +":guilabel:`Generate Offer`: 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` to send " +"an email to the employee, so they can sign the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:250 +msgid "" +"At the bottom of the pop-up form is a :guilabel:`Link Expiration Date`. This" +" is the timeframe that the contract offer is valid for. By default, this " +"field is pre-populated with `30 days`, but it can be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:255 +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:258 +msgid "" +":guilabel:`Signature Request`: clicking this reveals a pop-up window, 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:264 +msgid "" +"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:268 +#: ../../content/applications/hr/payroll/salary_attachments.rst:3 +msgid "Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:270 +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:274 +msgid "" +"To add a new deduction, first navigate to :menuselection:`Payroll app --> " +"Contracts --> Salary Attachments`. Next, click :guilabel:`Create`, and a new" +" salary attachment form loads." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:-1 +msgid "" +"The salary attachment form with everything filled in for Ronnie Hart's child" +" support." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:283 +msgid "" +":guilabel:`Employee`: using the drop-down menu, select the employee the " +"salary attachment applies to." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:285 +msgid "" +":guilabel:`Description`: enter a short description for the salary " +"attachment, such as `Child Support` or `529 Contribution`." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:287 +msgid "" +":guilabel:`Type`: using the drop-down menu, select the type of salary " +"attachment being created." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:288 +msgid "" +":guilabel:`Start Date`: the date the salary attachment starts. Choose a date" +" by clicking on the drop-down menu, navigating to the correct month and year" +" by using the :icon:`fa-chevron-left` :icon:`fa-chevron-right` " +":guilabel:`(arrow)` icons, then clicking on the desired date. This field is " +"**required**." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:292 +msgid "" +":guilabel:`Estimated End Date`: this field automatically populates after " +"both the :guilabel:`Monthly Amount` and :guilabel:`Total Amount` fields are " +"populated. This field is **not** modifiable." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:295 +msgid "" +":guilabel:`Document`: attach any documents relevant to the salary " +"attachment. Click the :guilabel:`Upload Your File` button, navigate to the " +"desired document in the file explorer, then click :guilabel:`Open` to select" +" the document, and attach it to the form. To change the attached document, " +"click the :icon:`fa-pencil` :guilabel:`(pencil)` icon, and select a " +"different document. To remove a document, click the :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:300 +msgid "" +":guilabel:`Monthly Amount`: enter the amount to be taken out of the " +"employee's paycheck every month for this specific salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/contracts.rst:302 +msgid "" +":guilabel:`Total Amount`: enter the total amount that the employee pays for " +"the salary attachment to be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:5 +msgid "Payroll localizations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:7 +msgid "" +"*Localizations* are country-specific settings preconfigured in Odoo at the " +"creation of the database, which account for all taxes, fees, and allowances " +"for that particular country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:10 +msgid "" +"*Payroll localizations* refer to the specific process of adapting payroll " +"systems, policies, and compliance measures to align with the specific labor " +"laws, tax regulations, and social security requirements of a particular " +"country or region." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:14 +msgid "" +"This ensures that employee salaries, benefits, deductions, and contributions" +" are processed accurately and in full compliance with local legal and " +"financial obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:17 +msgid "" +"Localization also includes integrating country-specific payroll elements " +"such as benefits, holidays, termination rules, and reporting requirements, " +"helping businesses avoid legal risks while ensuring employees receive their " +"correct compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:22 +msgid "Install localization package" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:24 +msgid "" +"A country-specific localization module :ref:`must be installed " +"` to properly configure and process payroll. To install the" +" required module, first open the **Apps** app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:27 +msgid "" +"Clear out the default :icon:`fa-filter` :guilabel:`Apps` filter, then type " +"the name of the desired country into the search bar. All available modules " +"for that country are presented." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:31 +msgid "" +"Some countries only have one localization module, while other have multiple " +"modules. This is typically when other software is neede to process payroll, " +"and importing and exporting data is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:35 +msgid "" +"For example. when searching for **Payroll** modules for `Egypt`, the " +"following modules appear in the search, and must be installed: `Egypt - " +"Payroll` and `Egypt - Payroll with Accounting`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:38 +msgid "" +"Refer to the :ref:`country-specific documentation " +"` for a complete list of the related " +"**Payroll** modules required for each specific country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:42 +msgid "" +"To see if any localization modules have been installed on the database, " +"navigate to :menuselection:`Payroll app --> Configuration --> Settings`. In " +"the :guilabel:`Settings` page, if a localization module was installed, a " +":guilabel:`(Country) Localization` section appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:47 +msgid "" +"It is **not** recommended to alter the localization settings, unless " +"specifically required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:50 +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, must be set up as their own company/branch using the " +"multi-company method." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:56 +msgid "" +"Each individual company can have a different localization setting, since " +"locations can vary anywhere in the world, where rules and laws differ." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:59 +msgid "" +"For more information on companies, refer to the :doc:`Companies " +"<../../general/companies>` documentation, which covers how to set up " +"companies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:65 +msgid "List of countries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:67 +msgid "" +"Payroll localization modules are available for the countries listed below." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:70 +msgid "" +"New countries are frequently added to this list, as Odoo keeps expanding and" +" improving existing localizations and related documentation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:73 +msgid ":doc:`Australia `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:74 +msgid ":doc:`Belgium `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:75 +msgid "Bangladesh" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:76 +msgid ":doc:`Egypt `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:77 +msgid ":doc:`Hong Kong `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:78 +msgid "India" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:79 +msgid "Indonesia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:80 +msgid ":doc:`Jordan `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:81 +msgid "Kenya" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:82 +msgid "Lithuania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:83 +msgid "Luxembourg" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:84 +msgid "Malaysia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:85 +msgid "Mexico" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:86 +msgid "Morocco" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:87 +msgid "Netherlands" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:88 +msgid "Pakistan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:89 +msgid "Poland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:90 +msgid "Romania" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:91 +msgid "Saudi Arabia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:92 +msgid "Slovakia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:93 +msgid "Switzerland" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:94 +msgid "Türkiye" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:95 +msgid "" +":doc:`United Arab Emirates `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations.rst:96 +msgid "United States" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:3 +msgid "Australia" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:8 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2 and " +"SuperStream. An announcement will be made as soon as companies can use Odoo " +"for payroll as a one-stop platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:12 +msgid "Setting up employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:15 +msgid "Employee settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:17 +msgid "" +"Create an employee by going to :menuselection:`Employees --> New`. Go to the" +" :guilabel:`Settings` tab, and configure the :guilabel:`Australian Payroll` " +"section, for example checking if they are :guilabel:`Non-resident`, if they " +"benefit from the :guilabel:`Tax-free Threshold`, their :guilabel:`TFN " +"Status`, :guilabel:`Employee Type`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employee settings tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:26 +msgid "Employee private information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:28 +msgid "" +"In addition, some personal employee information is required for payroll " +"compliance with Single Touch Payroll, and to process superannuation " +"payments. Open the employee's :guilabel:`Private Information` tab and fill " +"in the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:32 +msgid ":guilabel:`Private Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:33 +msgid ":guilabel:`Private Email`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:34 +msgid ":guilabel:`Private Phone`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:35 +msgid ":guilabel:`Date of Birth`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Employee private information tab for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:41 +msgid "" +"Odoo will remind you to complete the required data at different stages of " +"the process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:44 +msgid "Super accounts and funds" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:46 +msgid "" +"You can add the superannuation details of new employees under the employee's" +" :guilabel:`Super Accounts` tab. Click :guilabel:`Add a line` and make sure " +"to include the :guilabel:`Member Since` date, :guilabel:`Member Number`, and" +" :guilabel:`Super Fund`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:51 +msgid "" +"Use the :guilabel:`Proportion` field if an employee's contributions should " +"sent to multiple funds at a time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"Configuring a super fund and super account for the Australian payroll " +"localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:57 +msgid "" +"To create a new :guilabel:`Super Fund`, start typing its name and click " +":guilabel:`Create and edit...`. Fill in its:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:60 +msgid ":guilabel:`Address`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:61 +msgid ":guilabel:`ABN`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:62 +msgid ":guilabel:`Type` (APRA / SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:63 +msgid "unique identifier (:guilabel:`USI` for APRA, :guilabel:`ESA` for SMSF)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:64 +msgid "(for SMFS only) :guilabel:`Bank Account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a super fund for the Australian payroll localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:70 +msgid "" +"Manage all super accounts and funds by going to :menuselection:`Payroll --> " +"Configuration --> Super Funds` or :menuselection:`Super Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:74 +msgid "Odoo is currently in the process of becoming SuperStream-compliant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:79 +msgid "" +"Once the employee has been created, create their employment contract by " +"clicking the :icon:`fa-book` :guilabel:`Contracts` smart button, or by going" +" to :menuselection:`Employees --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:84 +msgid "" +"Only one contract can be active per employee at a time. However, an employee" +" can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:88 +msgid "Employment contract creation: recommended steps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Recommended steps to create an employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:94 +msgid "1. Basic contractual information" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:96 +msgid "" +"Select the :guilabel:`Contract Start Date` and :guilabel:`Working Schedule` " +"(set, or flexible for casual workers)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:98 +msgid "" +"Keep the :guilabel:`Salary Structure Type` set to :guilabel:`Australian " +"Employee`. This structure covers all of the ATO's tax schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:103 +msgid "" +"(if using the Attendances or Planning app) Select the :guilabel:`Work Entry " +"Source` to define how working hours and days are accounted for on the " +"employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:106 +msgid "" +":guilabel:`Working Schedule`: work entries are automatically generated based" +" on the employee's working schedule, starting from the contract's start " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:110 +msgid "" +"An employee works 38 hours a week, their contract begins on 01/01, today's " +"date is 16/01, and the user generates a pay run from 14/01 to 20/01. The " +"working hours on the payslip will be automatically calculated to be 38 hours" +" (5 * 7.36 hours) if no unpaid leave is taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:114 +msgid "" +":guilabel:`Attendances`: the working schedule is ignored, and work entries " +"are only generated after clocking in and out of the Attendances app. Note " +"that attendances can be imported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:116 +msgid "" +":guilabel:`Planning`: the working schedule is ignored, and work entries are " +"generated from planning shifts in the Planning app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:120 +msgid "" +"Timesheets do not impact work entries in Odoo. If you need to import your " +"timesheets in Odoo, import them by going to :menuselection:`Payroll --> Work" +" Entries --> Work Entries` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:124 +msgid "2. Salary Information tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:126 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for full-time and part-" +"time employees, and :guilabel:`Hourly Wage` for casual workers. The latter " +"allows you to add a :guilabel:`Casual Loading` percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:131 +msgid "" +"For hourly workers, the :guilabel:`Hourly Wage` field should exclude casual " +"loading." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:133 +msgid "" +":guilabel:`Schedule Pay`: in Australia, only the following pay run " +"frequencies are accepted: :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Bi-weekly` (or fortnightly), :guilabel:`Monthly`, and " +":guilabel:`Quarterly`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:136 +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 computed automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:140 +msgid "3. Australia tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Australia tab of a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:145 +msgid ":guilabel:`General`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:147 +msgid "Add the :guilabel:`Regular Pay Day` if relevant." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:148 +msgid "" +"Enable :guilabel:`Report in BAS - W3` if you choose to add PAYG withholding " +"amounts in BAS section W3 instead of W2 (refer to the `ATO's web page on " +"PAYG withholding `_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:153 +msgid ":guilabel:`Leave loading / workplace giving`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:155 +msgid "" +"Define whether your employees are :guilabel:`Eligible for Leave Loading`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:156 +msgid "" +"Set the :guilabel:`Workplace Giving Employee` amount in exchange for " +"deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:157 +msgid "" +"Set the :guilabel:`Salary Sacrificed Workplace Giving` amount (e.g., " +"receiving a benefit instead of a deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:160 +msgid ":guilabel:`Super contributions`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:162 +msgid "" +"Add the :guilabel:`Extra Negotiated Super %` on top of the *super " +"guarantee*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:163 +msgid "" +"Add the :guilabel:`Extra Compulsory Super %` as per industrial agreements or" +" awards obligations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:165 +msgid ":guilabel:`Salary sacrifice`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:167 +msgid "" +":guilabel:`Salary Sacrifice Superannuation` allows employees to sacrifice " +"part of their salary in favor of reportable employer superannuation " +"contributions (RESC)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:169 +msgid "" +":guilabel:`Salary Sacrifice Other Benefits` allows them to sacrifice part of" +" their salary towards some other form of benefit (refer to the `ATO's web " +"page on Salary sacrificing for employees " +"`_ for more " +"information)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:175 +msgid "" +"As of Odoo 18, salary sacrificing for other benefits currently does not " +"impact fringe benefits tax (FBT) reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:181 +msgid "4. Salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:183 +msgid "" +"If the employee is to receive additional recurring payments every pay run, " +"whether indefinitely or for a set number of periods, click the :icon:`fa-" +"book` :guilabel:`Salary Attachments` smart button on the contract. Choose a " +":guilabel:`Type` and a :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:188 +msgid "" +"Around 32 recurring salary attachment types exist for Australia. These are " +"mostly related to allowances and child support. `Contact us " +"`_ for more information as to whether allowances " +"from your industry can be covered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:193 +msgid "5. Run the contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a running contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:198 +msgid "" +"Once all the information has been completed, change the contract stage from " +":guilabel:`New` to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:202 +msgid "Prepare pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:205 +msgid "Regular" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:207 +msgid "" +"Pay runs are created by going to :menuselection:`Payroll --> Payslips --> " +"Batches`. After clicking :guilabel:`New`, enter a :guilabel:`Batch Name`, " +"select a :guilabel:`Period`, and click :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to generate payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:214 +msgid "" +"Employees on a pay run can be filtered down by :guilabel:`Department` and " +":guilabel:`Job Position`. There is no limit to the amount of payslips that " +"can be created in one batch. After clicking :guilabel:`Generate`, one " +"payslip is created per employee in the :guilabel:`Waiting` stage, in which " +"they can be reviewed and amended before validation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Generated payslips in the waiting stage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:222 +msgid "On the payslip form view, there are two types of inputs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:224 +msgid "" +":guilabel:`Worked days` are computed based on the :ref:`work entry source " +"set on the employee's contract `. " +":ref:`Work entries can be configured ` " +"according to different types: attendance, overtime, Saturday rate, Sunday " +"rate, public holiday rate, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:228 +msgid "" +":guilabel:`Other inputs` are individual payments or amounts of " +":ref:`different types ` (allowances, lump" +" sums, deductions, termination payments, leaves, etc.) that have little to " +"do with the hours worked during the current pay period. The :ref:`previously" +" configured salary attachments ` are " +"simply recurring other inputs attached to a contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Worked days and other inputs of a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:237 +msgid "" +"Under the :guilabel:`Salary Computation` tab, Odoo automatically computes " +"payslip rules based on employees, contracts, worked hours, other input " +"types, and salary attachments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:240 +msgid "" +"The salary structure *Australian Employee* has 35 payslip rules that " +"automatically compute and dynamically display according to the payslip " +"inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Salary computation tab of a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:248 +msgid "The following rules apply for that pay period in the above example:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:250 +msgid ":guilabel:`Basic Salary`: pre-sacrifice gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:251 +msgid "" +":guilabel:`Ordinary Time Earnings`: amount to which the super guarantee " +"percentage needs to be applied" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:253 +msgid "" +":guilabel:`Salary Sacrifice Total`: includes the $150 sacrificed to " +"superannuation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:254 +msgid "" +":guilabel:`Taxable Allowance Payments`: includes the $10 allowance (*cents " +"per KM* in this case)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:256 +msgid "" +":guilabel:`Taxable Salary`: gross salary amount minus non-taxable amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:257 +msgid "" +":guilabel:`Salary Withholding` and :guilabel:`Total Withholding`: amounts to" +" be withheld from the taxable salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:259 +msgid ":guilabel:`Net Salary`: the employee's net wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:260 +msgid "" +":guilabel:`Concessional Super Contribution`: in this scenario, the amount " +"sacrificed to superannuation, payable to the employee's super fund in " +"addition to the super guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:262 +msgid "" +":guilabel:`Super Guarantee`: as of 01 July 2024, it is computed as 11.5% of " +"the ordinary time earnings amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:266 +msgid "" +"As of Odoo 18, the most recent tax schedule rates (2024-2025) have been " +"updated for all salary rules and computations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:270 +msgid "Out-of-cycle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:272 +msgid "" +"In Australia, payslips created without a batch are considered to be *out-of-" +"cycle* runs. Create them by going to :menuselection:`Payroll --> Payslips " +"--> Individual Payslips`. The same payslip rules apply, but the way these " +"payslips are submitted to the ATO in the frame of Single Touch Payroll (STP)" +" is slightly different." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:278 +msgid "" +"As of Odoo 18, adding an out-of-cycle payslip to an existing batch is " +"**not** recommended." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:281 +msgid "Finalise pay runs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:284 +msgid "Validate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:286 +msgid "" +"Once all payslip data is deemed correct, click :guilabel:`Create Draft " +"Entry` on the payslip batch. This can also be done payslip by payslip for " +"control reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:289 +msgid "This has several impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:291 +msgid "Marking the batch and its payslips as :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:292 +msgid "" +"Creating a draft accounting entry per payslip or one entry for the whole " +"batch, depending on your payroll settings. At this stage, accountants can " +"post entries to affect the balance sheet, P&L report, and BAS report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:295 +msgid "" +"Preparing the STP submission (or payroll data to be filed to the ATO as part" +" of STP compliance). This needs to be performed by the :guilabel:`STP " +"Responsible` user, defined under :menuselection:`Payroll --> Configuration " +"--> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:298 +msgid "" +"Preparing super contribution lines as part of SuperStream compliance. This " +"needs to be done by the :guilabel:`HR Super Send` user selected under " +":menuselection:`Payroll --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a draft payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:306 +msgid "Submit payroll data to the ATO" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:309 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" this step described above does not submit data yet to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:312 +msgid "" +"As per ATO requirements, STP submission for a pay run needs to be done on or" +" before the payday. For this reason, submit your STP data to the ATO first " +"before proceeding with payment. To do so, click :guilabel:`Submit to ATO` on" +" the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:316 +msgid "" +"On the STP record for this pay run, a few useful information is displayed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:318 +msgid "a warning message if important information is missing," +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:319 +msgid "an automatically generated activity for the STP responsible user, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:320 +msgid "" +"a summary of payslips contained in this pay run, auditable from this view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an STP record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:325 +msgid "" +"Once the STP record is ready to go, click :guilabel:`Submit to ATO`, then " +"read and accept the related terms and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:329 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:219 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:333 +msgid "Pay employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:331 +msgid "" +"Once the ATO submission is complete, you can proceed to pay your employees. " +"To facilitate the payment matching process, remember to post the payslip-" +"related journal entries prior to validating a payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:335 +msgid "" +"Although you may decide to pay your employees individually, we recommend " +"creating a batch payment from your payslip batch. To do so, click " +":guilabel:`Pay` on the payslip batch, and select :guilabel:`ABA Credit " +"Transfer` as the :guilabel:`Payment Method`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Selecting the payment method for a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:342 +msgid "This has two impacts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:344 +msgid "Marking the batch and its payslips as :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:345 +msgid "Creating a :guilabel:`Payment Batch` linked to the payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a paid batch of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:350 +msgid "" +"When receiving the bank statement in Odoo, you can now match the statement " +"line with the batch payment in one click. The payment is not reconciled " +"against the payslip batch, and all individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Steps to reconcile a bank statement with a batch payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:358 +msgid "Impact on accounting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:360 +msgid "" +"Depending on the employee and contract configuration, the journal entry " +"linked to a payslip will be more or less exhaustive." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:364 +msgid "" +"For instance, here is the journal entry generated by the employee Marcus " +"Cook configured above." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of a journal entry for a payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:369 +msgid "" +"Once posted, predefined accounts will impact the company's balance sheet " +"(PAYGW, wages, and superannuation liabilities) and profit & loss report " +"(wages and superannuation expenses). In addition, the employee's gross wage " +"and PAYG withholding will update the BAS report for the relevant period (see" +" Tax Grid: W1 and W2). Accounts can be adjusted to the company's chart of " +"accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a BAS report PAYG tax witheld section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:378 +msgid "Other payroll flows" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:381 +msgid "Paying super contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:384 +msgid "" +"Odoo has a partnership with a clearing house to process both superannuation " +"payments and data to the right funds in one click, via direct debit. Odoo is" +" currently in the process of becoming compliant with SuperStream, and an " +"announcement will be made as soon as superannuation contributions can be " +"processed via Odoo's payroll solution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:389 +msgid "" +"Once a quarter (or more frequently, in preparation for `Payday Super " +"`_), you have to process " +"superannuation payments to your employees' super funds. To do so, go to " +":menuselection:`Payroll --> Reporting --> Super Contributions`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:397 +msgid "" +"When ready to pay, add the :guilabel:`Bank Journal` that will be used to pay" +" the super from, then click :guilabel:`Lock` to prevent the contributions " +"from subsequent payslips from being added to that file. Instead, a new Super" +" file will be created." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:401 +msgid "" +"Once the payment has been processed, it can be traced back to the Super file" +" and matched with a bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of a super file payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:408 +msgid "Terminating employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:410 +msgid "" +"Employees can be terminated by going to :menuselection:`Payroll --> " +"Reporting --> Terminate Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:413 +msgid "The following fields must be completed:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:415 +msgid "" +":guilabel:`Contract End Date`: once the termination is validated, this date " +"will be added to the contract automatically, and mark the contract as " +":guilabel:`Expired` when the date has been reached." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:418 +msgid "" +":guilabel:`Cessation Type Code`: a mandatory field for the ATO's STP " +"reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:419 +msgid "" +":guilabel:`Termination Type`: the type of redundancy (genuine or non-" +"genuine) affects the computation of unused annual and long service leave " +"withholding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Terminating the contract of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:425 +msgid "" +"The balance of unused annual leaves and long service leaves is displayed for" +" reference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:427 +msgid "" +"Confirming the termination creates an out-of-cycle payslip with the tag " +":guilabel:`final pay`. It computes the worked days until the contract end " +"date, in addition to the employee's unused annual and long service leave " +"entitlements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Example of an out-of-cycle payslip of a terminated employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:434 +msgid "" +"Odoo automatically computes unused leave entitlements based on the " +"employee's current hourly rate leave loading (for annual leaves only), and " +"the remaining leave balance. However, these amounts can be manually edited " +"in the :guilabel:`Other Inputs` table if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:438 +msgid "" +"Employment Termination Payments (ETP) can also be added to the " +":guilabel:`Other Inputs` table. Odoo has a comprehensive list of excluded " +"and non-excluded ETPs for companies to select from." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Adding employment termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:445 +msgid "" +"Withholding for unused leaves and ETPs is computed according to the ATO's " +"`Schedule 7 `_ and `Schedule 11 `_ and updated as of 01 July 2024." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:451 +msgid "" +"Once an employee has been terminated and the last detailed of their " +"employment resolved, you can archive the employee by clicking the :icon:`fa-" +"cog` (:guilabel:`Actions`) icon, then :icon:`oi-archive` :guilabel:`Archive`" +" on the employee's form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:456 +msgid "Switching from another STP software to Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:458 +msgid "" +"When switching from another STP-enabled software to Odoo, you might need to " +"maintain the continuity in the YTD values of your employees. Odoo allows " +"importing employees' YTD values by going to :menuselection:`Payroll --> " +"Configuration --> Settings` and clicking :guilabel:`Import YTD Balances`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Import YTD balances button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:466 +msgid "" +"For the ATO to recognize the employee records of your previous software and " +"keep a continuity in Odoo, you must enter the:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:469 +msgid ":guilabel:`Previous BMS ID` (one per database)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:470 +msgid ":guilabel:`Previous Payroll ID` (one per employee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:472 +msgid "" +"Ask your previous software provider if you cannot find its BMS ID or your " +"employees' payroll IDs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Importing YTD balances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:477 +msgid "" +"This will give you the opportunity to add your employees' YTD opening " +"balances in the current fiscal year. The ATO reports on a lot of different " +"types of YTD. These are represented by the 13 following :guilabel:`Salary " +"Rules` in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Salary rules for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:485 +msgid "" +"Let us say that the employee Marcus Cook has been transitioned from another " +"STP-enabled software on September 1. Marcus has received two monthly " +"payslips in his previous software (for July and August). Here are the YTD " +"balances Marcus's company needs to transfer to Odoo:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:492 +msgid "YTD category" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:493 +msgid "YTD balance to transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:494 +msgid "Gross (normal attendance)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:495 +msgid "$13,045.45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:496 +msgid "Gross (overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:497 +msgid "$1,000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:498 +msgid "Paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:499 +msgid "$954.55" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:500 +msgid "Laundry allowance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:501 +msgid "$200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:502 +msgid "Total withholding" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:503 +msgid "$2,956" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:504 +msgid "Super Guarantee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:505 +msgid "$1,610" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:507 +msgid "" +"If some YTD balances need to be reported with more granularity to the ATO, " +"you can use the salary rule's inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:511 +msgid "" +"For instance, the *Basic Salary* rule can contain six inputs, and three are " +"necessary in our example: regular gross amounts, overtime, and paid leaves. " +"These are all reported differently in terms of YTD amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Adding YTD inputs" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:518 +msgid "" +"The finalized YTD opening balances for Marcus Cook look like the following." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Example of finalized YTD opening balances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:523 +msgid "" +"As a result, YTD computations on payslips are based on the employee's " +"opening balances instead of starting from zero." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:527 +msgid "STP finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:530 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the finalisation flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:534 +msgid "EOFY finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:536 +msgid "" +"Employers reporting through STP must make a finalization declaration by 14 " +"July each year. To do so, go to :menuselection:`Payroll --> Reporting --> " +"STP Finalisation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "EOFY finalisation of an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:542 +msgid "Both active and terminated employees to finalise are displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "List of employees to finalise." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:547 +msgid "" +"From the finalisation form view, you can proceed with a final audit of all " +"employees' payslips during the relevant financial year. Once ready, click " +":guilabel:`Submit to ATO`. When you have made the finalisation declaration, " +"employees will see the status of their payment information change to " +":guilabel:`Tax ready` on their online income statement after the end of the " +"financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:553 +msgid "Individual finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:555 +msgid "" +"Odoo also allows you to finalise employees individually during the year. " +"This can be useful when:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:557 +msgid "one-off payments are made after a first finalisation; and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:558 +msgid "finalisation after termination of employment during the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:560 +msgid "" +"To proceed with an individual finalisation, go to :menuselection:`Payroll " +"--> Reporting --> STP Finalisation`, leave the :guilabel:`EOFY Declaration` " +"checkbox unticked, and manually add employees to be finalised." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Individual EOFY finalisation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:567 +msgid "" +"Even if you finalise an employee record partway through the financial year, " +"the ATO will not pre-fill the information into the employee's tax return " +"until after the end of the financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:571 +msgid "Adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:574 +msgid "" +"Odoo is currently in the process of becoming compliant with STP Phase 2, and" +" the adjustment flows described below do not yet submit data to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:578 +msgid "Amend finalisation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:580 +msgid "" +"If you need to amend YTD amounts for an employee after a finalisation " +"declaration was made, it is still possible to remove the finalisation " +"indicator for that employee. To do so, go to :menuselection:`Payroll --> " +"Reporting --> STP Finalisation`, select the employee, and leave the " +":guilabel:`Finalisation` checkbox unticked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Amending YTD amounts for an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:588 +msgid "" +"When ready, click :guilabel:`Submit to ATO` to file the finalisation update " +"to the ATO." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:590 +msgid "" +"Once the correct YTD details are ready for that employee after amendment, " +"finalise that employee again." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:594 +msgid "" +"The ATO expects employers to correct errors within 14 days of detection or, " +"if your pay cycle is longer than 14 days (e.g., monthly), by the date you " +"would be due to lodge the next regular pay event. Finalisation amendments " +"can be done through STP up to five years after the end of the financial " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:599 +msgid "" +"Finalising and amending finalisation for a single employee can also be " +"useful when rehiring an employee within the same financial year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:603 +msgid "Full file replacements" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:605 +msgid "" +"An employer can make full file replacements of pay runs to replace the last " +"lodgement sent to the ATO if it turns out to contain significantly " +"inaccurate data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:608 +msgid "" +"To do so, open the last STP submission and click :guilabel:`Replace File`. " +"Then, select which payslips need to be reset by ticking the :guilabel:`Reset" +" Payslip` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Replace file button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:614 +msgid "" +"Resetting payslips does not create new payslips or a new pay run, but " +"instead:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:616 +msgid "" +"The payslips batch is reset from :guilabel:`Paid` or :guilabel:`Done` to " +":guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:617 +msgid "The status of the reset payslips revert back to :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:618 +msgid "" +"The correct payslips remain paid and matched against the original payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:619 +msgid "" +"A new STP submission is created to replace the former one. For traceability " +"purposes, the former STP submission is not deleted but marked as replaced." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:622 +msgid "" +"First, correct the reset payslips and create their draft entry. Once done, " +"the :guilabel:`Submit to ATO` reappears on the payslip batch to process the " +"full file replacement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Resubmitting a payslip batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:628 +msgid "" +"When ready, submit the pay run to the ATO once again. Please note that full " +"file replacements are only meant as a last resort to amend a substantial " +"amount of erroneous data. When possible, the ATO recommends correcting an " +"incorrect payslips by submitting a correction as part of the next pay run or" +" via update event." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:633 +msgid "" +"Moreover, it is not possible to submit a second full file replacement of the" +" same submission, and a full file replacement can only be done once every 24" +" hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:637 +msgid "Zero out YTD values" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:639 +msgid "" +"In case of a mid-year change of several key identifiers, YTD values need to " +"be zeroed out, and then re-posted with the updated key identifier." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:642 +msgid "" +"For the following **company identifiers**, all employees need to be zeroed " +"out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:644 +msgid "ABN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:645 +msgid "Branch Code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:646 +msgid "BMS ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:648 +msgid "" +"For the following **employee identifiers**, only individual employees can be" +" zeroed out:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:650 +msgid "TFN" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:651 +msgid "Payroll ID" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:653 +msgid "" +"Before updating any key identifiers, create a new STP submission by going to" +" :menuselection:`Payroll --> Reporting --> Single Touch Payroll` and:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:656 +msgid "Change the :guilabel:`Submission Type` to :guilabel:`Update`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:657 +msgid "Tick the :guilabel:`Zero Out YTD` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:658 +msgid "Click :guilabel:`Add a line` to specify which employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:659 +msgid "Click :guilabel:`Submit to ATO`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Creating a new STP submission to zero out YTD values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:664 +msgid "Once that is done, modify the key identifier(s) to amend." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:666 +msgid "" +"Finally, go back to :menuselection:`Payroll --> Reporting --> Single Touch " +"Payroll` to create and submit a new :guilabel:`Update`, this time without " +"ticking the :guilabel:`Zero Out YTD` checkbox. This will notify the ATO that" +" the previously recorded YTD balances are to be adjusted to the new key " +"identifiers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:672 +msgid "Payroll links to other apps" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:675 +msgid "Time Off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:677 +msgid "" +"The :doc:`Time Off app <../../../hr/time_off>` is natively integrated with " +"the Payroll app in Odoo. Different types of leaves will populate payslips " +"based on the concept of *work entries*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:680 +msgid "" +"Go to :menuselection:`Time Off --> Configuration --> Time Off Types`, and " +"for each type, configure the following two fields under the " +":guilabel:`Payroll` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:683 +msgid "" +":guilabel:`Work Entry Type`: defines which work entry should be selected on " +"the :guilabel:`Worked Days` table of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:685 +msgid "" +":guilabel:`Unused Leave Type`: choose between :guilabel:`Annual`, " +":guilabel:`Long Service`, or :guilabel:`Personal Leave`. If " +":guilabel:`Personal Leave` is selected, the remaining leave balance for this" +" time off type will not show up as an entitlement at the time of " +"termination. Unused leaves of the type :guilabel:`Annual` will include leave" +" loading if the employee is eligible for it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring time off types." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:695 +msgid "Expenses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:697 +msgid "" +"The :doc:`Expenses app <../../../finance/expenses>` is also natively " +"integrated with the **Payroll** app in Odoo. First of all, go to " +":menuselection:`Expenses --> Configuration --> Settings` and enable " +":guilabel:`Reimburse in Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:701 +msgid "" +"When an employee on your payroll submits an approved expense to be " +"reimbursed, you can reimburse them using two ways:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:704 +msgid "" +"If the expense is to be reimbursed outside of a pay run, click " +":guilabel:`Post Journal Entries`. The payment must be made manually." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:706 +msgid "" +"If the expense is to be reimbursed as part of the next pay run, click " +":guilabel:`Report in Next Payslip` instead." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Two ways of reimbursing an expense." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:712 +msgid "" +"After an expense has been added to the next payslip, you can find it in the " +":guilabel:`Other Inputs` table. This input type is then computed as an " +"addition to the net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "The expense reimbursement on a payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:718 +msgid "" +"After paying the employee, the payslip's journal item related to the " +"employee's reimbursement is automatically matched against the expense's " +"vendor bill." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "" +"The payslip's journal item related to the employee's expense reimbursement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:725 +msgid "Advanced configurations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:732 +msgid "" +"You can access other input types by going to :menuselection:`Payroll --> " +"Configuration --> Other Input Types`. There are 63 other input types related" +" to Australia. We do not recommend using the other ones as part of your " +"payroll solution, since they cannot be used in the frame of STP. You can " +"archive or delete them." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:737 +msgid "On each input type, the following fields are important:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:739 +msgid ":guilabel:`Payment Type` classifies input types in six categories:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:741 +msgid "" +":guilabel:`Allowance`: a separate amount you pay to your employees in " +"addition to salary and wages. Some of these allowances are mandated by " +"modern awards: laundry, transport, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:745 +msgid "" +"`Contact us `_ if you plan to use allowances " +"subject to varied rates of withholding (such as *cents per KM* or *travel " +"allowances*) to see whether Odoo currently covers your business case." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:750 +msgid "" +"As of Odoo 18, some allowances such as :guilabel:`Laundry: Allowance for " +"approved uniforms` are managed by two other inputs: one to lodge the amount " +"paid up to the ATO limit, and the other one to lodge the amount exceeding " +"the ATO limit. This is necessary for Odoo to compute PAYGW correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:754 +msgid "" +"Some businesses may require to shift the reporting of an allowance from " +":guilabel:`OTE` to :guilabel:`Salary & Wages` depending on the employee. In " +"this case, you must duplicate and re-configure an existing other input type." +" For example, :guilabel:`Work-Related Non-Expense` allowance is " +":guilabel:`OTE` by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:759 +msgid "" +":guilabel:`Deduction`: union fees and child support deductions are " +"considered deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:760 +msgid "" +":guilabel:`ETP`: employment termination payments. These are either " +"considered excluded or non-excluded (see `ATO's web page on ETP components " +"taxation `_)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:762 +msgid "" +":guilabel:`Leave`: leave-related other inputs that are not pertaining to a " +"single pay period (lump sum, cashing out leaves while in service, unused " +"leaves, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:764 +msgid "" +":guilabel:`Lump Sum`: return to work and lump sum E (for back payments) fall" +" under this category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:766 +msgid ":guilabel:`Other`: other payments with their own specific logic." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:768 +msgid "" +":guilabel:`PAYGW Treatment` affects how Odoo withholds tax for this input " +"type: :guilabel:`Regular`, :guilabel:`No PAYG Withholding`, and " +":guilabel:`Excess Only` (for allowances)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:771 +msgid "" +":guilabel:`Superannuation Treatment`: :guilabel:`OTE`, :guilabel:`Salary & " +"Wages`, and :guilabel:`Not Salary & Wages`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:773 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the gross value of this payment " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:777 +msgid "" +"Grouping other input types by :guilabel:`Payment Type` can help you " +"understand the different scenarios in which these inputs can be used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Other input types grouped by payment type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:788 +msgid "" +"A *work entry type* is a type of attendance for employees (e.g., attendance," +" paid leave, overtime, etc.). A few work entry types are created by default " +"in every Australian database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Default work entry types for the Australian localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:794 +msgid "" +"Before using Odoo's payroll solution for Australia, it is recommended you " +"trim work entry types to keep the ones you need only by going to " +":menuselection:`Payroll --> Configuration --> Work Entry Types`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:798 +msgid "" +"For each type, make sure to configure the following fields for Australia:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:800 +msgid "" +":guilabel:`Is OTE`: determines whether time spent in this category can be " +"considered ordinary time earnings, meaning that the superannuation guarantee" +" rate will apply (e.g., regular attendance, paid leave, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:803 +msgid "" +":guilabel:`Penalty Rate`: used to determine the percentage of penalty that " +"applies to time spent in this category. It is important that you configure " +"the penalty rate that applies in your state or industry according to the " +"type of work (e.g., Saturday rate, Sunday rate, overtime rate, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:806 +msgid "" +":guilabel:`STP Code`: only visible in :ref:`developer mode `, this field tells Odoo how to report the time spent in this category " +"to the ATO. We do not recommend changing the value of this field if it was " +"already set by default." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Configuring a work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:814 +msgid "Current limitations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:816 +msgid "" +"As of Odoo 18, we do not recommend companies to use the Payroll app for the " +"following business flows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:819 +msgid "Income stream types: Foreign Employment Income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:820 +msgid "Tax treatment category: actors & performers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:821 +msgid "Death benefits reporting" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:822 +msgid "Reporting obligations for WPN (instead of ABN)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:823 +msgid "" +"Allowances subject to a varied rate of withholding (such as *cents per " +"kilometer* allowance and *travel allowances*)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:826 +msgid "" +"`Contact us `_ if you would like to make sure " +"whether Odoo fits your payroll requirements in Australia." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:832 +msgid "Employment Hero integration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:834 +msgid "" +"If your business is already up and running with Employment Hero, you can use" +" the connector as an alternative payroll solution. The Employment Hero " +"module synchronizes payslip accounting entries (e.g., expenses, social " +"charges, liabilities, taxes) automatically from Employment Hero to Odoo. " +"Payroll administration is still done in Employment Hero; Odoo only records " +"the journal entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:842 +msgid "" +":ref:`Install ` the Employment Hero Payroll module " +"(`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:843 +msgid "" +"Configure the Employment Hero API by going to :menuselection:`Accounting -->" +" Configuration --> Settings`. More fields become visible after ticking the " +":guilabel:`Enable Employment Hero Integration` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Enabling the Employment Hero integration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:850 +msgid "" +"Find the :guilabel:`API Key` in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero API key under the My Account section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:856 +msgid "" +"The :guilabel:`Payroll URL` is pre-filled with " +"`https://keypay.yourpayroll.com.au`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:859 +msgid "Do not change the pre-filled :guilabel:`Payroll URL`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:861 +msgid "" +"Find the :guilabel:`Business Id` in the Employment Hero URL (e.g., " +"`189241`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:0 +msgid "Finding the Employment Hero Business ID in the URL." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:866 +msgid "" +"Select any Odoo journal as the :guilabel:`Payroll Journal` to post the " +"payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:868 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from Employment Hero in the " +":menuselection:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:873 +msgid "The API explained" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:875 +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:56 +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/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Employment Hero journal entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:882 +msgid "" +"By default, the synchronization happens once per week. It is possible to " +"fetch the records manually by going to :menuselection:`Accounting --> " +"Configuration --> Settings` and, in the :guilabel:`Employment Hero`, " +"clicking :guilabel:`Fetch Payruns Manually`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:886 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +" The accounts used by Employment Hero are defined in the Payroll settings " +"section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:-1 +msgid "Finding the Employment Hero accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/australia.rst:892 +msgid "" +"For the API to work, you must 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/hr/payroll/payroll_localizations/belgium.rst:3 +msgid "Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:8 +msgid "Understanding the Belgian payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:13 +msgid "" +"Providing employees with a clear, transparent payslip is essential for " +"compliance and employee satisfaction. This guide explains how to interpret a" +" Belgian payslip, detailing key components that impact salary calculations " +"and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:20 +msgid "" +"The first section of the payslip contains the employee's general details. It" +" is crucial to verify the accuracy of the civil status and the number of " +"dependents, as these factors influence tax calculations. Employers can " +"ensure updates are made through their internal salary configurator or " +"employee profile management systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - General Information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:31 +msgid "" +"This section outlines time-off applications and their impact on salary. The " +"base salary typically remains constant unless unpaid leave is taken. If an " +"employee has taken unpaid leave, parental leave, or any unexpected absence, " +"their salary will reflect the corresponding deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "How to read a payslip - Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:39 +msgid "Payroll calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:41 +msgid "" +"The core of the payslip details various salary components, deductions, and " +"benefits. Below are the primary elements:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:44 +msgid "" +"**Benefits in Kind**: If applicable, benefits in kind (such as a mobile or " +"internet subscription or a laptop) are subject to taxation and impact net " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:47 +msgid "" +"When a company car is provided for personal use, a taxable benefit (ATN) is " +"added to the employee's salary. This is determined by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:50 +msgid "The catalog value and age of the vehicle" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:51 +msgid "The vehicle's CO2 emissions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:53 +msgid "" +"This benefit is subject to withholding tax and will be adjusted later in the" +" payroll process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:54 +msgid "" +"**Social Security contributions**: A mandatory 13.07% deduction from gross " +"salary is allocated to the National Social Security Office (ONSS). This " +"includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:57 +msgid "Pensions: 7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:58 +msgid "Health Insurance for Care: 3.55%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:59 +msgid "Health Insurance for Benefits: 1.15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:60 +msgid "Unemployment: 0.87%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:62 +msgid "" +"Additionally, the employer contributes on average 25% of the employer's " +"contributions to the National Social Security Office." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:64 +msgid "" +"**Employment bonus**: A reduction in employee contributions based on gross " +"salary, which is phased out if the salary exceeds a specific threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:68 +msgid "" +"`More info on job bonuses " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:70 +msgid "" +"**Withholding taxes**: Withholding tax rates are revised annually by the " +"`SPF Finances " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:73 +msgid "The tax amount is influenced by:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:75 +msgid "Gross salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:76 +msgid "Marital status (married, legally cohabiting, or single)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:77 +msgid "Household composition (children or other dependents)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:79 +msgid "This serves as an advance payment on professional income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:80 +msgid "" +"**Reduction in withholding tax**: A reduction based on gross salary, which " +"is ignored if salary surpasses a specific amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:82 +msgid "" +"**Special Social Security contribution**: A household income-based tax " +"applicable to all employees covered by social security." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:84 +msgid "" +"**Meal voucher deduction**: Employees receive meal vouchers valued for " +"instance at €8 per workday, where:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:87 +msgid "The employer contributes €6.91" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:88 +msgid "The employee contributes €1.09" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:91 +msgid "5 worked days -> deduction of €5.45 (:math:`5\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:92 +msgid "22 worked days -> deduction of €23.98 (:math:`22\\times\\text{€}1.09`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:94 +msgid "Variations in this deduction impact monthly net salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:95 +msgid "" +"**Representation fees**: An optional net salary component, allocated in two " +"parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:97 +msgid "A fixed portion, independent of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:98 +msgid "A prorated portion, adjusted for part-time schedules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:99 +msgid "" +"**Net salary**: The final amount deposited into the employee's bank account " +"after deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:104 +msgid "December pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:107 +msgid "Why a December settlement?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:109 +msgid "" +"An employer must pay a vacation allowance to an employee in December under " +"two conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:111 +msgid "" +"If the employee has reduced their working hours during the vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:112 +msgid "" +"If the employee is unable to take all their vacation days before the end of " +"the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:114 +msgid "" +"In principle, employers must ensure that employees take their annual " +"vacation before December 31. However, certain circumstances may prevent " +"employees from using all their vacation days. In these cases, the employer " +"must pay the simple vacation allowance for unused days before the end of the" +" year. Additionally, if the employee has not received the double vacation " +"allowance earlier in the year (typically in May or June), they are entitled " +"to receive it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:121 +msgid "Reduction of working hours" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:123 +msgid "" +"When an employee reduces their average working hours with the same employer," +" the employer must pay the vacation allowance in December of the year in " +"which the reduction occurs, as if the employee had left the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:127 +msgid "**Possible scenarios**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:129 +msgid "Transition to part-time work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:130 +msgid "Partial career break." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:131 +msgid "Thematic leave on a part-time basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:132 +msgid "Partial return to work after a full incapacity period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:134 +msgid "" +"The settlement is calculated based on the previous vacation year's earnings " +"and includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:136 +msgid "" +"**Simple vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the simple vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:139 +msgid "" +"**Double vacation allowance**: 7.67% of the yearly gross salary from the " +"previous year, including any fictitious salary for assimilated interruption " +"days, minus the double vacation allowance already paid during the vacation " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:143 +msgid "" +"If all vacation days have been taken before the reduction in working hours, " +"no additional calculation is required." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:147 +msgid "Inability to use vacation days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:149 +msgid "" +"As a general rule, all vacation days must be used within the vacation year. " +"However, if an employee is unable to take all their vacation due to force " +"majeure or specific suspension reasons, the employer must pay the following " +"by December 31:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:153 +msgid "" +"**Simple vacation allowance** for unused days, based on the December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:154 +msgid "" +"**Double vacation allowance** if it has not yet been paid, based on the " +"December salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:156 +msgid "**Eligible reasons include**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:158 +msgid "Common illness or accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:159 +msgid "Work accident or occupational disease." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:160 +msgid "" +"Maternity leave, paternity leave (converted maternity leave), prophylactic " +"leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:161 +msgid "Birth, adoption, or reception leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:162 +msgid "Parental leave or protective maternity leave measures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:165 +msgid "New rule (effective end of 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:167 +msgid "" +"Employees unable to take vacation due to the above reasons (except force " +"majeure or protective maternity leave measures) can carry over unused days " +"for up to 24 months. Since the vacation allowance is already paid in " +"December of the vacation year, no additional payment will be made when the " +"carried-over days are used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:173 +msgid "Employer payment responsibilities" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:175 +msgid "" +"The employer must pay any outstanding simple vacation allowance based on " +"7.67% of the gross salary from the previous year. However, an exit vacation " +"allowance based on the current year's gross salary is not due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:179 +msgid "" +"If an employee reduces their working hours and continues in the same role " +"the following year, an additional vacation allowance calculation may be " +"required in December." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:183 +msgid "Example calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:185 +msgid "In 2013, an employee works full-time (5 days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:186 +msgid "" +"In 2014, the employee works full-time until June 30, then switches to part-" +"time (5 half-days per week)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:188 +msgid "" +"The employee takes vacation in August 2014 under the new part-time regime " +"(20 half-days over 4 weeks)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:190 +msgid "" +"They receive a simple vacation allowance for 20 half-days and a double " +"vacation allowance equivalent to 92% of their monthly salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:192 +msgid "" +"In December 2014, the employee receives additional simple (7.67%) and double" +" (7.67%) vacation allowances based on 2013's gross salary, minus previously " +"paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:194 +msgid "" +"In 2015, if the employee continues part-time, they receive vacation based on" +" part-time hours plus 5 full-time vacation days from the 2014 vacation year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:196 +msgid "" +"A second settlement in December 2015 includes additional simple (7.67%) and " +"double (7.67%) vacation allowances based on the 2014 gross salary, minus " +"previously paid amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1650 +msgid "How to do it in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:202 +msgid "" +"On a classic :doc:`payslip <../payslips>` issued in December, press the " +":guilabel:`Compute December Holiday Pay` button to open a configuration " +"wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:205 +msgid "" +"Based on the allocated and requested time off, the :guilabel:`Simple Holiday" +" Pay N-1` and :guilabel:`Double Holiday Pay N-1` for the December payslip " +"are computed (and editable for manual encoding). Click :guilabel:`Validate` " +"to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:212 +msgid "" +"After validation, two additional inputs are stored on the payslip, and the " +"payslip is re-computed to take those new remunerations into account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:215 +msgid "The simple holiday pay is included into the gross remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Simple." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:220 +msgid "" +"The double holiday pay is computed separately and included into the net " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "December Pay Double." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:228 +msgid "Departure: holiday attests" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:233 +msgid "" +"In Belgium, when an employee leaves a company, the employer is required to " +"provide vacation attestations. These documents help the new employer " +"determine the employee's vacation entitlements and any vacation pay due. " +"Odoo facilitates the automatic generation of these attestations based on " +"payroll and time-off data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:239 +msgid "Types of attestations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:241 +msgid "Odoo generates two types of vacation attestations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:243 +msgid "" +"**For the previous year (N-1)**: If the employee has not yet taken all the " +"vacation days from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:245 +msgid "" +"**For the current year (N)**: Covering the vacation rights accrued in the " +"year of departure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:247 +msgid "Each attestation includes details such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:249 +msgid "The period the employee was employed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:250 +msgid "Agreed working time and any modifications." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:251 +msgid "Gross amounts of single and double vacation pay paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:252 +msgid "Social security contributions paid by the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:253 +msgid "Number of vacation days already taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:254 +msgid "Additional (European) vacation pay and days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:257 +msgid "Calculation logic in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:259 +msgid "" +"Odoo computes the attestations based on payroll and leave data. The main " +"calculations include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:261 +msgid "**Retrieving payroll and leave records**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:263 +msgid "" +"The system identifies the employee's payroll records for the current and " +"previous years." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:264 +msgid "It retrieves validated leave requests and allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:266 +msgid "**Computing gross remuneration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:268 +msgid "" +"The gross annual salary for both the current and previous years is computed " +"from payroll records." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:270 +msgid "The average monthly salary is calculated for unpaid leave adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:272 +msgid "**Time-off calculations**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:274 +msgid "" +"The number of vacation days taken and allocated in the current year is " +"determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:275 +msgid "Unpaid leave days are accounted for separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:277 +msgid "**Fictitious remuneration calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:279 +msgid "" +"If unpaid leave was taken, Odoo computes a fictitious remuneration " +"adjustment using the formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:282 +msgid "" +"\\text{Fictitious Remuneration} = (\\text{Unpaid Leave Days} \\times\n" +"\\text{Average Monthly Salary} \\times 3) \\div (13 \\times 5)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:288 +msgid "**Generating the final attestation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:290 +msgid "Odoo creates a payroll entry reflecting the vacation pay due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:291 +msgid "The attestation document is generated and can be printed or exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:293 +msgid "Two payslips are created:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:295 +msgid "**Payslip for the current year** (`termination_payslip_n`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:297 +msgid "" +"This payslip covers the employee's last salary period in the year of " +"termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:299 +msgid "**Payslip for the previous year** (`termination_payslip_n1`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:301 +msgid "" +"The one accounts the amount of money converted from the untaken time off of " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:303 +msgid "" +"Each payslip is generated using the appropriate payroll structure, ensuring " +"correct calculations for all entitlements and deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:306 +msgid "" +"Before computing the final payment, the system gathers necessary payroll " +"data:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:308 +msgid "**Annual gross salary calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:310 +msgid "" +"To estimate the employee's **annual gross salary**, the system looks for the" +" most recent validated monthly payslip. If a payslip is found, the **gross " +"salary** from that payslip is multiplied by 12 to get an annual estimate. If" +" no payslip exists, the annual gross salary is set to **zero**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:315 +msgid "**European leave recovery**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:317 +msgid "" +"The system retrieves all **European leave days (LEAVE216)** taken by the " +"employee during the current year. It then calculates the **total amount paid" +" for these leaves** and determines how much should be deducted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:321 +msgid "The deduction follows these principles:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:323 +msgid "" +"If an employee has taken **European holidays (additional vacation days)**, " +"the amount paid in advance must be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:325 +msgid "The recovery is either:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:327 +msgid "Deducted from **the double vacation pay (85%)** for the next year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:328 +msgid "" +"Or, if the employee leaves, deducted from the final termination payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:330 +msgid "If leave has been taken, the **termination certificate** must specify:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:332 +msgid "The **number of European leave days** already granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:333 +msgid "The **gross allowance** corresponding to these days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:335 +msgid "" +"To ensure fairness, the system first checks whether a deduction has already " +"been applied in the **double vacation pay**. If so, only the remaining " +"amount is deducted from the final payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:338 +msgid "" +"Once the required values are determined, they are recorded in the payslip as" +" **additional payroll inputs**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:341 +msgid "" +"**Gross salary reference**: Includes the final salary amount plus any " +"fictitious remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:342 +msgid "" +"**European leave deduction**: Deducts the previously paid European leave " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:343 +msgid "" +"**Other inputs**: Allocates time off taken, taxable amounts, and any " +"outstanding allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:345 +msgid "" +"After setting these values, the system **computes the payslip** to ensure " +"all deductions and payments are correctly applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:348 +msgid "" +"This process ensures that the final **termination payslip** takes into " +"account all salary components, including **annual gross pay, European leave " +"recovery, and any unpaid entitlements**. Odoo retrieves past payslips and " +"time-off records to ensure compliance with **Belgian payroll regulations**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:353 +msgid "" +"By automating this process, Odoo minimizes manual intervention, reducing " +"errors and ensuring employees receive the correct termination payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:357 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:609 +msgid "How does it work in Odoo?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:359 +msgid "" +"In Odoo, to access the holiday attests process, go to the employee form view" +" and click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure:" +" Holiday Attests` or navigate to :menuselection:`Payroll --> Reporting --> " +"Departure: Holiday Attests`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:363 +msgid "" +"In the wizard that appears, you can see all the payslips over the current " +"and last year, the time off requests and allocations. You can also encode " +"the unpaid time off you would like to declare on that holiday attest." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:367 +msgid "" +"Once you're ready, click the :guilabel:`Validate & Compute holiday attests` " +"button. Two payslips are generated for each considered period (N and N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:370 +msgid "" +"Once validated, two :file:`.pdf` documents are generated. One **classic " +"payslip** and one **holiday attests** for the future employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Unpaid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:387 +msgid "" +"In our example, the employee also took one European time off during the " +"N-year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:389 +msgid "For year N-1, you can see that all legal time off were taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N-1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:397 +msgid "" +"For year N, you can also see the number off additional time off (European) " +"and already taken legal time off are taken into account as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Attest N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Holiday Attests Payslip N." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:407 +msgid "Important Notes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:409 +msgid "" +"By using Odoo's automated attestation generation, companies can ensure " +"compliance with Belgian labor laws while reducing manual administrative " +"work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:413 +msgid "The feature is only available for companies registered in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:414 +msgid "" +"If the notice period is not set for an employee, Odoo will prompt for this " +"information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:415 +msgid "" +"Employers must ensure vacation attestations are provided before the employee" +" needs to submit them to their new employer or the ONEM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:421 +msgid "Departure: notice period & termination fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:423 +msgid "" +"This documentation explains how the employee departure process works in the " +"application, focusing on the notice period calculation and severance pay " +"when the employee does not serve their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:430 +msgid "" +"This module helps manage employee departures by determining the correct " +"notice period based on seniority, departure reasons, and specific country " +"regulations (Belgium). It also calculates severance pay when the employee " +"does not work during their notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:435 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:78 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:124 +msgid "Key features" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:437 +msgid "Automatic calculation of notice period start and end dates." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:438 +msgid "Consideration of public holidays and company-specific schedules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:439 +msgid "" +"Calculation of severance pay based on company policies and government rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:440 +msgid "Generation of a final payslip including termination fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:443 +msgid "Notice period calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:445 +msgid "The notice period depends on several factors:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:447 +msgid "The employee's seniority in the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:448 +msgid "The reason for departure (resignation, dismissal, retirement, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:449 +msgid "Whether the employee works during the notice period or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:450 +msgid "The salary level before January 1, 2014 (for some cases)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:452 +msgid "" +"The notice period starts on the first Monday after the departure date unless" +" a specific rule applies (e.g., a mandatory waiting period of three days for" +" certain dismissals)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:456 +msgid "Notice duration rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:458 +msgid "" +"The following table shows the duration of the notice period based on the " +"length of service:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:461 +msgid "For resigned employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Seniority (months)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:464 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:493 +msgid "Notice Period (weeks)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +msgid "0 - 3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:466 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:495 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "1" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +msgid "3 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:468 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +msgid "6 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:470 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "3" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +msgid "12 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:472 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +msgid "18 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:474 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +msgid "24 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:476 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "48 - 60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:478 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "7" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "60 - 72" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:480 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "72 - 84" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:482 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "84 - 96" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:484 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +msgid "96+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:486 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "13" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:490 +msgid "For dismissed employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:497 +msgid "3 - 4" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:499 +msgid "4 - 5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:501 +msgid "5 - 6" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:503 +msgid "6 - 9" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:505 +msgid "9 - 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +msgid "12 - 15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:507 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "8" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:509 +msgid "15 - 18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:511 +msgid "18 - 21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +msgid "21 - 24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:513 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "11" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:515 +msgid "24 - 36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:517 +msgid "36 - 48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:519 +msgid "15" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:521 +msgid "18" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:523 +msgid "21" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:525 +msgid "24" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "96 - 108" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:527 +msgid "27" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +msgid "108 - 120" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:529 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:330 +msgid "30" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "120 - 132" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:531 +msgid "33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "132 - 144" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:533 +msgid "36" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "144 - 156" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:535 +msgid "39" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "156 - 168" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:537 +msgid "42" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "168 - 180" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:539 +msgid "45" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "180 - 192" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:541 +msgid "48" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "192 - 204" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:543 +msgid "51" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "204 - 216" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:545 +msgid "54" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "216 - 228" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:547 +msgid "57" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "228 - 240" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:549 +msgid "60" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "240 - 252" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:551 +msgid "62" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "252 - 264" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:553 +msgid "63" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "264 - 276" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:555 +msgid "64" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "276 - 288" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:557 +msgid "65" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "288+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:559 +msgid "66+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:563 +msgid "Special case: employees hired before 2014" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:565 +msgid "" +"For employees who started before January 1, 2014, the notice period " +"calculation is divided into two parts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:569 +msgid "Part 1: Seniority acquired before December 31, 2013" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:571 +msgid "" +"**Lower-level employees** (annual gross salary ≤ €32,254): The notice period" +" is 3 months for the first 5 years of seniority, increasing by 1.5 months " +"per additional year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:573 +msgid "" +"**Higher-level employees** (annual gross salary > €32,254): The notice " +"period is 1 month per started year of seniority, with a minimum of 3 months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:577 +msgid "Part 2: Seniority acquired from January 1, 2014 onwards" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:579 +msgid "" +"The standard notice period rules from 2014 apply to seniority acquired after" +" this date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:581 +msgid "" +"The total notice period is the sum of both periods calculated separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:584 +msgid "Severance pay calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:586 +msgid "" +"If an employee does not serve their notice period, severance pay is " +"calculated based on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:588 +msgid "The remaining notice duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:589 +msgid "The employee's last salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:590 +msgid "" +"Additional compensation such as bonuses, stock options, and insurance " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:592 +msgid "The severance pay consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:594 +msgid "" +"The current salary, which corresponds either to the full notice period that " +"should normally be observed or the remaining part of it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:596 +msgid "" +"Benefits acquired during the contract (e.g., meal vouchers, company car, " +"mobile phone usage)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:598 +msgid "The current salary is determined as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:600 +msgid "The employee's gross monthly salary at the time of dismissal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:601 +msgid "" +"All recurring bonuses, except for one-time bonuses (e.g., team work bonus, " +"seniority bonus)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:602 +msgid "" +"Additional compensation for overtime hours worked over a longer period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:603 +msgid "Variable salary (average over the last twelve months)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:605 +msgid "" +"The system automatically generates a termination payslip including these " +"calculations, ensuring compliance with Belgian labor laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:611 +msgid "" +"In Odoo, to access the departure process, go to the employee form view and " +"click on :icon:`fa-cog` :guilabel:`(Action)` then :guilabel:`Departure: " +"Notice Period and payslip` or navigate to :menuselection:`Payroll --> " +"Reporting --> Departure: Notice Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:615 +msgid "" +"In the wizard that appears, select the reason for departure, provide a " +"description of the departure, and specify the dismissal date. The employee's" +" seniority is calculated based on their contract history, and the notice " +"period is determined accordingly. You can also indicate whether the employee" +" will be working during the notice period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Departure Notice Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:623 +msgid "" +"If the employee is working during the notice period, there are no " +"termination fees to calculate, and the notice period will be recorded on the" +" employee's form. Click the :guilabel:`Validate` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:627 +msgid "" +"If the employee is working partially or not at all, the wizard will generate" +" and calculate a termination fees payslip. Click the :guilabel:`Validate & " +"Compute termination fees` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:630 +msgid "" +"The payslip takes into account all the salaries and benefits the employee " +"would have received over the course of a year to calculate a virtual annual " +"remuneration. This amount is then prorated based on the notice period to " +"convert it into a gross salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:634 +msgid "A detailed summary is provided on the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Departure Notice: Termination Fees Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:644 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1354 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2118 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2253 +msgid "Conclusion" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:646 +msgid "" +"This module simplifies the departure process by providing clear and " +"automatic calculations for the notice period and severance pay. It helps HR " +"teams ensure compliance and streamline the exit process for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:653 +msgid "DIMONA" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:656 +msgid "What is the Dimona?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:659 +msgid "Obligation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:661 +msgid "" +"All employers, both in the public and private sectors, are required to " +"electronically communicate the entry and exit of their personnel to the " +"National Social Security Office (Royal Decree of November 5, 2002)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:665 +msgid "" +"This involves the immediate declaration of employment, also known as DIMONA " +"(Déclaration Immédiate - Onmiddellijke Aangifte). Its purpose is to " +"immediately notify social security institutions of the beginning and end of " +"an employment relationship between the worker and the employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:669 +msgid "" +"The declarations submitted by the employer and immediately checked by the " +"NSSO feed into a database called the *personnel file*. The employer can " +"access it in a secure environment. There are numerous search criteria: they " +"can be based on characteristics and combinations of characteristics." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:673 +msgid "" +"Failure to comply with this reporting obligation may result in criminal " +"penalties as provided for in Article 181 of the Social Penal Code." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:676 +msgid "" +"Furthermore, in case of omission of declaration, the employer will owe the " +"NSSO a solidarity contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:680 +msgid "Concept and terminology" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:683 +msgid "Employer-worker relationship" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:685 +msgid "" +"The relationship between the \"employer\" and the \"worker\" couple. This " +"relationship includes stable data (employer identification number, worker's " +"national identification social security number (NISS), start date of the " +"relationship, and optionally end date), which will be maintained even in " +"case of creation, closure, modification, or cancellation of a period. This " +"relationship begins with the worker's first engagement and ends at the end " +"of their last occupation. In the personnel file, \"employer-worker\" " +"relationships constitute the first level of consultation. The second level " +"encompasses all Dimona periods;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:694 +msgid "Dimona period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:696 +msgid "" +"A period is created with each IN declaration, thus at the beginning of each " +"new occupation. It is closed by an exit date at the end of each occupation. " +"The employer-worker relationship, on the other hand, is maintained until the" +" end of the last occupation. Several Dimona periods may or may not succeed " +"each other within the same employer-worker relationship." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:701 +msgid "" +"Any changes generated by an OUT declaration, a modification (UPDATE), or a " +"cancellation (CANCEL) occur at this second level." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:704 +msgid "" +"This Dimona period is identified by a \"period identification number\". It " +"is assigned to each IN declaration and constitutes the unique identification" +" key of a period for submitting OUT, modification, or cancellation " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:709 +msgid "Dimona number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:711 +msgid "" +"A unique number assigned by the NSSO to each Dimona declaration (IN, OUT, " +"UPDATE, CANCEL,...). For an IN declaration, it is the period identification " +"number. When declarations are submitted via file transfer, multiple Dimona " +"numbers are created: one number per employment relationship included in the " +"structured message;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:717 +msgid "Dimona characteristics" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:719 +msgid "" +"Mandatory data of a Dimona declaration. There are four: the industry sector " +"number, worker type, sub-entity (reserved for certain public sector " +"employers), and user (for temporary workers). Characteristics are always " +"linked to a period. In case of different characteristics, multiple periods " +"can coexist;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:725 +msgid "Receipt confirmation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:727 +msgid "" +"Confirms for web users that the declaration has been received (appears " +"immediately on the screen);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:730 +msgid "Receipt acknowledgment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:732 +msgid "" +"Electronic message for batch senders indicating whether the file is usable " +"for the NSSO. This \"receipt acknowledgment\" contains the ticket number " +"(:dfn:`file identification number`) and the file status: accepted or " +"rejected depending on whether the file is readable or not;" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:737 +msgid "Notification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:739 +msgid "" +"Electronic message with feedback on the processing of the declaration. The " +"notification is the immediate result of form and content checks. It can be " +"of three types: positive (Dimona accepted), negative (Dimona rejected), or " +"provisional (only in case of problems with worker identification). The " +"provisional notification will always be followed by a positive or negative " +"notification." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:744 +msgid "" +"For the declaration of students under a student contract (STU), the " +"notification will also contain a warning if the student is declared for more" +" than 475 hours. If the declaration was made via a secure channel, the exact" +" number of days of excess will be communicated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:748 +msgid "" +"For the daily declaration of occasional workers in the hospitality industry," +" the notification will also contain a warning if the worker is declared for " +"more than 50 days and/or for the employer quota, if more than 100 days of " +"occasional work have been declared." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:752 +msgid "" +"Once you have received this notification, you have five working days to " +"contest the accuracy of the data mentioned therein. At the end of this " +"period, these data will be considered final. For any disputes, you must " +"contact the Eranova Contact Center (tel: 02 511 51 51, email: " +"contactcenter@eranova.fgov.be)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:757 +msgid "" +"Note that if the employer is affiliated with an approved social secretariat " +"or a full-service secretariat, they may not receive any notification. In " +"this case, notifications are electronically transmitted to the social " +"secretariat or full-service secretariat, even for declarations that the " +"employer has submitted personally. However, the employer has access to the " +"personnel file, where they can view all data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:764 +msgid "Channels" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:766 +msgid "" +"The Dimona declaration must be submitted in the form of an electronic " +"message via one of the following channels:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:769 +msgid "web" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:770 +msgid "personnel file" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:771 +msgid "file transfer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:772 +msgid "web service (REST)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:773 +msgid "Dimona Mobile" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:775 +msgid "" +"The choice of one channel over another has no impact on the declaration. " +"Therefore, you can freely choose the channel you will use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:778 +msgid "" +"Any declaration modifications can also be made through any of these four " +"channels. The channel through which the original declaration was submitted " +"plays no role." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:781 +msgid "A Dimona declaration cannot be submitted via SMS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:784 +msgid "Dimona in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:787 +msgid "Manual" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:789 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, as soon " +"as you have a contract set to the running stage, it creates an activity for " +"the HR responsible that they need to introduce the Dimona for today with the" +" correct link to the Dimona Platform (the web channel mentioned in the " +"Channels section of this article)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Dimona Activity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:798 +msgid "Automated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:800 +msgid "" +"In Odoo, when you have the Belgian Payroll Localization installed, it is " +"also possible to install the module Belgium - Payroll - Dimona. This module " +"will allow you to perform the 4 main actions needed in the Dimona (as seen " +"in Section 1 of this article):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:804 +msgid "Open the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:805 +msgid "Update the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:806 +msgid "Close the dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:807 +msgid "Cancel the Dimona" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:809 +msgid "These actions answer the different use case explained in Section 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:812 +msgid "Contract and employee data" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:814 +msgid "" +"Basically, it checks the contract and employee data needed to create, " +"update, close or cancel." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:817 +msgid "Error handling" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:819 +msgid "" +"If some information is missing or wrongly configured, the system will return" +" errors and you can take corrective action in order to make sure your Dimona" +" is correctly sent, updated, closed or canceled." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:824 +msgid "Synchronization status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:826 +msgid "" +"The status of sync and errors are shown in the chatter of the contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:829 +msgid "Scheduled action" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:831 +msgid "" +"Finally, the cron checks every day, for all contracts that have the status " +"dimona waiting and triggers the necessary actions to update the dimona " +"status accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:835 +msgid "Technical configuration (outside Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:837 +msgid "" +"Regarding the technical configuration, everything is described in the module" +" information with all the technical prerequisites. If your customer or " +"partner need further assistance with that, they need to contact their IT " +"department or representatives as this is not part of Odoo configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:842 +msgid "Functional configuration (within Odoo)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:844 +msgid "" +"From the Odoo configuration point of view, navigate to " +":menuselection:`Payroll app --> Configuration --> Settings` and in the " +":guilabel:`Belgian Localization` section for :guilabel:`ONSS`, configure the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:848 +msgid ":guilabel:`ONSS Company ID`: VAT Number of the Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:849 +msgid "" +":guilabel:`Registration Number`: 9 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:850 +msgid "" +":guilabel:`DMFA Employer Class`: 3 digits code received from the NSSO (ONSS " +"- RSZ)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:851 +msgid "" +":guilabel:`Expeditor Number ONSS`: Not Mandatory (see technical " +"documentation of the module for more information)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:853 +msgid "" +":guilabel:`PEM Certificate`, :guilabel:`PEM Passphare`, :guilabel:`KEY " +"file`: check the module information for explanation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:859 +msgid "DmfA - Multifunctional Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:864 +msgid "" +"DmfA stands for \"Déclaration Multifonctionnelle\" or \"Multifunctionele " +"Aangifte.\" It has replaced the quarterly ONSS declaration since the first " +"quarter of 2003. Through this declaration, employers submit salary and " +"working time data for their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:868 +msgid "" +"These data are processed in a way that allows all social security " +"institutions to work with the same information. The declaration is called " +"\"multifunctional\" because it is used not only for social security " +"contribution calculations and reductions but also as a data source for " +"institutions managing social security rights and benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:873 +msgid "Sectors utilizing DmfA data include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:875 +msgid "Health insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:876 +msgid "Unemployment benefits" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:877 +msgid "Pensions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:878 +msgid "Occupational risks (Fedris)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:879 +msgid "Family allowances" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:880 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:89 +msgid "Annual leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:882 +msgid "All employers registered with ONSS must submit a DmfA declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:885 +msgid "Relationship with Dimona and DRS" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:887 +msgid "DmfA is closely linked to two other mandatory declarations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:890 +msgid "Dimona (immediate declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:892 +msgid "" +"Dimona records the start and end of an employment relationship with an " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:895 +msgid "DRS (social risks declaration)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:897 +msgid "" +"During an employment relationship, various social risks may arise, such as " +"termination, workplace accidents, or long-term illness. When a social risk " +"occurs, social security institutions require additional information beyond " +"that provided by DmfA and Dimona." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:901 +msgid "" +"DRS is now primarily an electronic declaration, though paper submissions " +"remain possible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:904 +msgid "Who submits the DmfA declaration?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:907 +msgid "Self-declaration options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:909 +msgid "Employers can submit their DmfA declaration themselves via:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:911 +msgid "" +"**Web Submission:** Suitable for employers with a small workforce. " +"Declarations are entered directly through the social security portal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:913 +msgid "" +"**Batch Submission:** Designed for large employers or organizations handling" +" multiple declarations (e.g., social secretariats, payroll software " +"providers). Declarations are submitted via file transfer (FTP, SFTP, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:918 +msgid "Advantages of web submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:920 +msgid "" +"**Automatic access to the company's employee list**: Based on Dimona data. " +"If an employee is missing, they must first be declared via Dimona. After 24 " +"hours, the employee list is updated, allowing for an accurate DmfA " +"submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:923 +msgid "" +"**Automatic calculation of net payable amount**: Once all required data is " +"entered, the system calculates the total payable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:925 +msgid "" +"**Reduction calculations**: The system calculates applicable reductions, " +"except for reductions under code \"0001\" (personal contribution reductions " +"for low-income workers). Employers need to check the relevant boxes and, if " +"necessary, provide additional details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:930 +msgid "Advantages of batch submission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:932 +msgid "" +"**Submission of large volumes of declarations**: Ideal for organizations " +"managing multiple payrolls." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:934 +msgid "" +"**Quick response on acceptance status**: Employers receive immediate " +"feedback on whether their declaration has been accepted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:936 +msgid "" +"**Error reporting**: The system generates a report on detected anomalies, " +"regardless of acceptance status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:938 +msgid "" +"**Automatic correction of calculation errors**: When possible, errors are " +"corrected automatically, and employers are notified of adjustments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:942 +msgid "Third-Party submission options" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:944 +msgid "" +"Employers who do not wish to submit the DmfA themselves can delegate the " +"task to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:946 +msgid "" +"**Accredited Social Secretariats**: These organizations handle payroll and " +"declaration tasks on behalf of employers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:948 +msgid "" +"**Service Providers**: These may be companies or individuals with whom the " +"employer has a contractual agreement to manage payroll declarations " +"securely." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:951 +msgid "" +"For more information on accredited social secretariats or service providers," +" please refer to the relevant `official DmfA documentation " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:958 +msgid "" +"The declaration is generated under :menuselection:`Payroll app --> Reporting" +" --> Belgium --> DmfA` as is supposed to work properly after several " +"required configuration steps." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:962 +msgid "Company" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:964 +msgid "" +"To generate a valid DmfA declaration, specific company and employer-related " +"information is required, (under :menuselection:`Payroll app --> " +"Configuration --> Settings`). These include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:967 +msgid ":guilabel:`ONSS Company ID`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:968 +msgid ":guilabel:`ONSS Registration Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:969 +msgid ":guilabel:`DMFA Employer Class`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:970 +msgid "" +":guilabel:`ONSS Certificate`: certificate for signature file generation " +"(required for batch declarations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:972 +msgid "VAT :guilabel:`Company Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:973 +msgid ":guilabel:`Revenue Code`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:974 +msgid ":guilabel:`FFE Employer Type` (Fonds de Fermeture d'Entreprise)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:979 +msgid "" +"Additionally, each employee must be assigned to a valid working address, " +"identified with a DmfA code, in their employee record. This operating unit " +"must be linked to a valid ONSS identification number to ensure compliance " +"with declaration requirements. Failing to configure this properly may result" +" in errors during the declaration submission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:984 +msgid "On the employee form, the :guilabel:`Work Address` must be defined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:986 +msgid "" +"Under :menuselection:`Payroll app --> Configuration --> DMFA: Work " +"Locations`, you can link the work address to a ONSS identification number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Work Location ONSS ID." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:993 +msgid "Work entry type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:995 +msgid "" +"A DmfA code should be defined for each work entry type that is declared. " +"Under :menuselection:`Payroll app --> Configuration --> Work Entries --> " +"Work Entry Types`, specify the :guilabel:`DMFA code`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1000 +msgid "Potential configuration errors" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1002 +msgid "" +"During the declaration generation process, configuration issues may arise, " +"triggering errors such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1005 +msgid "Terminated employees without or with invalid start/end notice period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1006 +msgid "Invalid NISS number for some employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1007 +msgid "Work addresses not linked to an ONSS identification code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1008 +msgid "Work entry type missing a corresponding DmfA code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1009 +msgid "Other inconsistencies in employer or employee records" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1011 +msgid "" +"Employers should ensure accurate configuration to avoid delays and rejection" +" of their declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1014 +msgid "Web declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - Web Declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1019 +msgid "" +"A web declaration generates a PDF summarizing the company's general " +"information, as well as all employee data that must be manually entered into" +" the system. This includes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1022 +msgid "For the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1027 +msgid "For a specific employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "DmfA - PDF Employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1032 +msgid "" +"**Occupations**: Work schedules, part-time codes, parental leave, " +"exploitation unit, reference working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1034 +msgid "" +"**Services**: Aggregated work performance (in days and hours) for the " +"quarter, categorized by occupation and type. The codification of working " +"time in the DmfA declaration ensures accurate reporting of employee " +"activities. Each code corresponds to a specific type of working time or " +"absence. For a complete and detailed list of codes, please refer to the " +"official social security website: `socialsecurity.be " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1040 +msgid "" +"**1**: All performances covered by a salary subject to ONSS contributions, " +"excluding legal and additional vacation for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1042 +msgid "**2**: Legal vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1043 +msgid "**3**: Additional vacation days for workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1044 +msgid "**4**: Compensatory rest days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1045 +msgid "**5**: Days of illness or non-occupational accident." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1046 +msgid "**6**: Family leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1047 +msgid "**7**: Maternity or paternity leave days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1048 +msgid "**8**: Strike days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1049 +msgid "**9**: Temporary unemployment for economic reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1050 +msgid "**10**: Temporary unemployment for bad weather." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1051 +msgid "**11**: Temporary unemployment for force majeure." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1052 +msgid "**12**: Professional training days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1053 +msgid "**13**: Suspension for disciplinary reasons." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1054 +msgid "**14**: Additional vacation days for employment start or resumption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1055 +msgid "**15**: Flexible vacation days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1057 +msgid "**Remunerations**: Aggregated by code per occupation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1059 +msgid "**1**: Regular salary amounts excluding certain indemnities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1060 +msgid "" +"**2**: Bonuses and similar benefits granted independently of actual working " +"days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1061 +msgid "**3**: Severance payments expressed in working hours." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1062 +msgid "" +"**7**: Simple vacation pay for exiting employees (subject to contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1063 +msgid "**10**: Personal use of a company vehicle and other mobility benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1064 +msgid "" +"**11**: Simple vacation pay for exiting employees (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1065 +msgid "" +"**12**: Advance vacation pay paid by a previous employer (not subject to " +"contributions)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1067 +msgid "**Contributions**: Employer and employee contributions, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1069 +msgid "**256**: Asbestos fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1070 +msgid "**255**: Special work accident contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1071 +msgid "**495**: Total employer + 13.07% employee contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1072 +msgid "**809**: Enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1073 +msgid "**810**: Special enterprise closure fund contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1074 +msgid "**831**: Auxiliary Joint Committee for Employees (CP200) contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1075 +msgid "**855**: Wage restraint contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1076 +msgid "**856**: Special social security contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1077 +msgid "**859**: Temporary unemployment contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1080 +msgid "Batch declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1085 +msgid "" +"Batch declarations require technical knowledge, including SSH keys, SFTP " +"servers, and electronic signatures. Employers should refer to the `official " +"batch documentation " +"`_" +" and `process overview " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1090 +msgid "A batch submission generates three files:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1092 +msgid "**Declaration file** (e.g., FI.DMFA.112768.20250109.00014.R.1.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1093 +msgid "**Launch file** (e.g., GO.DMFA.112768.20250109.00014.R.1)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1094 +msgid "" +"**Electronic signature file** (e.g., FS.DMFA.112768.20250109.00014.R.1.1) " +"(only for real declarations, not tests)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1097 +msgid "" +"The full process includes creating, sending, validating, and potentially " +"correcting declarations. Rejections and anomalies must be addressed before " +"final acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1103 +msgid "**Creation of the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1105 +msgid "" +"Create an XML document containing employee benefit data, remuneration, and " +"contributions for the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1107 +msgid "" +"More information on XML files can be found in the *Specifications* page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1109 +msgid "**Sending the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1111 +msgid "" +"Use FTP or SFTP for sending the file. Access requires prior authorization " +"for secure zone access by a local manager." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1113 +msgid "" +"Detailed instructions are available on the `Introduce and Modify (via batch)" +" `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1116 +msgid "**File Acknowledgment Receipt**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1118 +msgid "" +"**Positive Receipt**: Indicates the file can be processed. However, this " +"does not guarantee acceptance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1120 +msgid "" +"**Negative Receipt**: Indicates issues with the file structure or access " +"rights." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1122 +msgid "**Notification and Ticket Number for the Declaration**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1124 +msgid "A positive notification is sent for each accepted declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1125 +msgid "Negative notification: Provides information on encountered anomalies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1127 +msgid "**Sending PID**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1129 +msgid "" +"Employers and SSA will receive PID and version numbers via batch for " +"declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1131 +msgid "**Modification Notification with System Corrections**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1133 +msgid "" +"If corrections are made, a modification notification is sent with corrected " +"values." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1138 +msgid "Double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1140 +msgid "" +"Double holiday pay is an additional bonus paid to employees and workers " +"during their annual leave. The amount depends on the employee's or worker's " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1144 +msgid "How is double holiday pay calculated?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1146 +msgid "" +"For employees, double holiday pay amounts to 92% of their gross salary for " +"the month when they take their main annual leave. This amount is calculated " +"based on the number of months worked or considered equivalent in the " +"previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1151 +msgid "Impact of additional or European leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1153 +msgid "" +"If you take additional or European leave, your employer will pay you regular" +" holiday pay for that leave. However, the following year, this amount will " +"be deducted from your double holiday pay. This is because additional leave " +"is considered an advance on the next year's legal leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1158 +msgid "Factors affecting the calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1160 +msgid "" +"**Months Worked**: The calculation is based on the number of months you " +"worked in the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1162 +msgid "" +"**Absences**: If you had unpaid absences, they may reduce your double " +"holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1163 +msgid "" +"**Variable Revenues**: Bonuses and commissions earned in the previous year " +"can impact the total amount of double holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1165 +msgid "" +"**Withholding Taxes**: The double holiday pay is subject to income tax " +"deductions, which depend on your annual earnings and family situation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1169 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1489 +msgid "Withholding tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1171 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1491 +msgid "" +"The withholding tax is calculated using a progressive rate system. The " +"process involves:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1173 +msgid "**Identify the Employee's Annual Taxable Revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1175 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1495 +msgid "" +"Compute the annualized salary, including benefits in kind (e.g., company " +"car, internet, mobile phone, laptop)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1177 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1497 +msgid "Apply reductions for dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1179 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1499 +msgid "**Apply Tax Rates**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1181 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1501 +msgid "" +"Use predefined tax brackets to determine the base withholding tax rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1182 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1502 +msgid "" +"If applicable, apply a reduction based on the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1185 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1505 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:146 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:96 +msgid "Tax brackets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1187 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1507 +msgid "" +"The withholding tax is applied progressively based on the following brackets" +" (as of 2025):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Lower Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Upper Bound" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1190 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1510 +msgid "Tax Rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "10,415.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1192 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1512 +msgid "0.00%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "10,415.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "13,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1194 +msgid "19.17%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "13,330.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "16,960.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1196 +msgid "21.20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "16,960.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "20,340.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1198 +msgid "26.25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "20,340.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "23,020.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1200 +msgid "31.30%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "23,020.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "25,710.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1202 +msgid "34.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "25,710.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "31,070.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1204 +msgid "36.34%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "31,070.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "33,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1206 +msgid "39.37%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "33,810.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "44,770.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1208 +msgid "42.39%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "44,770.01" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "58,460.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1210 +msgid "47.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "∞" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1212 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1532 +msgid "53.50%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1216 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1536 +msgid "Tax exemption" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1218 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1538 +msgid "" +"A withholding tax exemption is granted when the normal annual gross income " +"does not exceed a specific threshold, which is determined based on the " +"number of dependent children [2]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1221 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1541 +msgid "A disabled dependent child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1223 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1543 +msgid "The method involves referring to a two-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1225 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1545 +msgid "**Column 1**: Indicates the number of dependent children." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1226 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1546 +msgid "" +"**Column 2**: Specifies the maximum allowable normal annual gross income, " +"based on the number of dependent children listed in Column 1, which must not" +" be exceeded to qualify for full or partial exemption from withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1230 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1550 +msgid "After determining the annual gross income, two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1232 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1552 +msgid "If the annual income exceeds the threshold, no exemption is granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1233 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1553 +msgid "" +"If the annual income does not exceed the threshold, an exemption will be " +"applied." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1235 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1555 +msgid "" +"The amount of this exemption corresponds to the difference between the " +"annual gross income and the threshold amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1238 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1558 +msgid "" +"Of course, if this difference exceeds the base withholding tax amount, no " +"withholding tax will be due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "No. of Children" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1242 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1562 +msgid "Max Revenue (EUR)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1244 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1564 +msgid "18,400.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1246 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1566 +msgid "21,930.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1248 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1568 +msgid "28,270.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1250 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1570 +msgid "35,330.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1252 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1572 +msgid "42,390.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1254 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1574 +msgid "49,450.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1256 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1576 +msgid "56,510.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1258 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1578 +msgid "63,570.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1260 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1580 +msgid "70,630.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1262 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1582 +msgid "77,690.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1264 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1584 +msgid "84,750.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1266 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1586 +msgid "91,810.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1270 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1590 +msgid "Tax reductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1272 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1592 +msgid "" +"When there is no justification for fully or partially exempting the " +"exceptional allowance from withholding tax, it is still possible to grant a " +"reduction in withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1275 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1595 +msgid "" +"To determine eligibility for this reduction, one must check whether the " +"normal annual gross salary exceeds a certain higher threshold, which varies " +"according to the number of dependent children [3]. This threshold is higher " +"than the one used for exemption purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1279 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1599 +msgid "A disabled child counts as two." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1281 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1601 +msgid "The method involves referring to a three-column table:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1283 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1603 +msgid "" +"**Column 1**: Indicates the number of dependent children (up to a maximum of" +" 5)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1284 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1604 +msgid "" +"**Column 2**: Specifies the percentage reduction in withholding tax, based " +"on the number of dependent children listed in Column 1, which must not be " +"exceeded to qualify for the reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1286 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1606 +msgid "" +"**Column 3**: Shows the threshold amount that must not be exceeded, " +"corresponding to the number of dependent children listed in Column 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1289 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1609 +msgid "Two scenarios may arise:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1291 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1611 +msgid "If the threshold amount is exceeded, no reduction will be granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1292 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1612 +msgid "" +"If the threshold amount is not exceeded, a reduction will be applied to the " +"withholding tax amount, up to a percentage rate determined in Column 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1295 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1615 +msgid "" +"For employees with dependent children, tax reductions apply as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Reduction (%)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1298 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1618 +msgid "Max Revenue" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +msgid "7.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1300 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1620 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "28,245.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1302 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1622 +msgid "20.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1304 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1624 +msgid "35.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "55.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1306 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1626 +msgid "36,720.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "5+" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "75.0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1308 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1628 +msgid "39,550.00" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1312 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1632 +msgid "Final tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1314 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1634 +msgid "The final withholding tax amount is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1316 +msgid "" +"\\text{Tax} = \\text{Gross Double Holiday} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1322 +msgid "" +"The resulting tax is deducted from the gross double holiday salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1325 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1645 +msgid "" +"The calculation considers work duration, absences, variable revenue, and " +"applicable withholding taxes. Odoo automates these calculations to ensure " +"compliance with Belgian labor laws and tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1330 +msgid "Generate a batch in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1332 +msgid "" +"Navigate to :menuselection:`Payroll App --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1335 +msgid "" +"Then click the **Generate Payslips** button, select the CP200 salary " +"structure type and the Thirteen Month salary structure. You can also filter " +"eligible employees by department and / or job position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1342 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1663 +msgid "Once validated, a payslip is generated for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1347 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1668 +msgid "" +"You can now check the different payslips before validation. Once validated, " +"the PDF files are generated and posted on employee portals as for classic " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Double Holiday PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1356 +msgid "" +"Double holiday pay is a significant benefit that rewards employees for their" +" work in the previous year. Understanding how it is calculated helps in " +"better financial planning for the holiday period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1362 +msgid "Eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1367 +msgid "" +"Eco vouchers are a tax-free employee benefit designed to support the " +"purchase of environmentally-friendly products and services. These vouchers " +"are ordered via external providers and are exempt from social security " +"contributions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1372 +msgid "Eligibility & allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1374 +msgid "" +"Employees who have worked during the **reference period (01/06/N-1 - " +"31/05/N)** are eligible for up to **250€** in eco vouchers, which are " +"granted at the beginning of **July**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1378 +msgid "" +"For 2025, employees must have worked between **01/06/2024 and 31/05/2025** " +"to qualify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1380 +msgid "" +"For employees who join during the reference period, the voucher amount is " +"prorated based on their worked days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1384 +msgid "" +"An employee hired on **06/01**, having worked **6 out of 12 months**, would " +"receive:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1386 +msgid "250\\text{€} \\times (6/12) = 125\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1391 +msgid "For part-time employees, the amount is adjusted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1396 +msgid "Work Regime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1397 +msgid "Voucher Amount (€)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1398 +msgid "4/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1399 +msgid "250€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1400 +msgid "3/5" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1401 +msgid "200€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1402 +msgid "1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1403 +msgid "125€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1404 +msgid "< 1/2" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1405 +msgid "100€" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1408 +msgid "" +"If an employee starts on **1st September** in **full-time** and then " +"switches to **half-time** on **1st April 2024**, the calculation will be:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1411 +msgid "250\\text{€} \\times (7/12) + 125\\text{€} \\times (2/12) = 166\\text{€}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1417 +msgid "Exceptions & adjustments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1419 +msgid "" +"If an employee worked full-time for the entire reference period but did not " +"receive **250€**, certain non-assimilated leave days may have affected the " +"calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1422 +msgid "" +"The following leave types are **not** considered for eco-voucher " +"entitlement:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1424 +msgid "**Unpaid leaves**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1425 +msgid "" +"**Sick leave compensated by mutual insurance** (after 30 days of work " +"incapacity)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1428 +msgid "Usage & validity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1430 +msgid "Eco vouchers are valid for **24 months** from the date of issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1433 +msgid "" +"The list of eligible products and services that can be purchased with eco " +"vouchers is available here:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1436 +msgid "" +"`Eco-Voucher Eligible Products `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1441 +msgid "End of year bonus" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1443 +msgid "" +"This document explains the calculation of the thirteenth-month salary (year-" +"end bonus) in Belgium within Odoo. The calculation considers the employee's " +"contracts, working time rates, and applicable taxes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1448 +msgid "Calculation of the thirteenth-month salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1451 +msgid "Eligibility criteria" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1453 +msgid "" +"The employee must have worked for at least **six complete months** in the " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1454 +msgid "" +"Both full-time and part-time employees are eligible, with prorated " +"calculations based on work time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1458 +msgid "Salary calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1460 +msgid "The thirteenth-month salary is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1462 +msgid "**Determine the basic salary**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1464 +msgid "Retrieve the employee's contractual wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1465 +msgid "Identify the applicable work rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1467 +msgid "**Compute eligible months**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1469 +msgid "" +"If explicitly provided (`MONTHS` input), use the given number of months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1470 +msgid "Otherwise, calculate the number of complete months worked." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1471 +msgid "Prorate the salary for partial-year work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1473 +msgid "**Adjust for absences**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1475 +msgid "Deduct unpaid absences to obtain the presence prorata." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1476 +msgid "Consider up to 60 days of sick leave as paid time off." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1478 +msgid "**Include variable revenues**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1480 +msgid "If explicitly provided (`VARIABLE` input), use the given value." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1481 +msgid "Otherwise, calculate the average variable revenue over the last year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1483 +msgid "**Final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1485 +msgid "" +"The final thirteenth-month amount is the sum of the prorated fixed salary " +"and average variable revenues." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1493 +msgid "**Identify the employee's annual taxable revenue**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1514 +msgid "23.22%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1516 +msgid "25.23%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1518 +msgid "30.28%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1520 +msgid "35.33%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1522 +msgid "38.36%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1524 +msgid "40.38%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1526 +msgid "43.41%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1528 +msgid "46.44%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1530 +msgid "51.48%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1636 +msgid "" +"\\text{Tax} = \\text{Gross Thirteenth Month} \\times \\text{Applicable Tax Rate} -\n" +"\\text{Reduction (if applicable)}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1642 +msgid "" +"The resulting tax is deducted from the gross thirteenth-month salary to " +"determine the net amount payable to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1652 +msgid "" +"Navigate to :menuselection:`Payroll app --> Payslips --> Batches` and create" +" a new record with valid dates (here december 2024)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1655 +msgid "" +"Then click the :guilabel:`Generate Payslips` button, select the " +":guilabel:`CP200: Belgian Employee` :guilabel:`Salary Structure Type` and " +"the :guilabel:`CP200: Employees 13th Month` :guilabel:`Salary Structure`. " +"You can also filter eligible employees by :guilabel:`Department` and / or " +":guilabel:`Job Position`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Batch Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus Payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "End of Year Bonus PDF." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1677 +msgid "Holiday pay recovery" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1679 +msgid "" +"This document explains how Odoo calculates the recovery of holiday pay (both" +" simple and double) for employees in Belgium who have changed employers. " +"When an employee moves from one company to another, their previous employer " +"may have already paid their holiday pay for the previous year. This amount " +"needs to be recovered by the new employer, and this guide outlines how this " +"is managed in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1685 +msgid "Understanding holiday pay in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1687 +msgid "" +"In Belgium, employees are entitled to annual leave and corresponding holiday" +" pay, which consists of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1689 +msgid "" +"**Simple holiday pay**: Regular salary payments for the days of leave taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1690 +msgid "" +"**Double holiday pay**: An additional payment, typically equal to " +"approximately 92% of the gross monthly salary, given when employees take " +"their annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1693 +msgid "" +"When an employee changes jobs, their previous employer may have already paid" +" these amounts. To avoid double payment, the new employer needs to recover " +"the amounts already paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1697 +msgid "Recovery of simple holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1699 +msgid "" +"The recovery of simple holiday pay in Odoo is based on the following " +"criteria:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1701 +msgid "" +"The recovery applies if the employee has taken leave in the current year and" +" their previous employer already paid the holiday pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1703 +msgid "" +"The calculation considers the number of leave days taken and the hours " +"worked per week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1704 +msgid "The recovery process is split into:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1706 +msgid "**Year N**: The current year's holiday pay recovery." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1707 +msgid "**Year N-1**: The recovery of holiday pay from the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1709 +msgid "The system checks:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1711 +msgid "" +"If the employee's first contract date with the company was in the previous " +"year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1712 +msgid "If the employee has a pending holiday pay recovery amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1713 +msgid "If the recovery has not already been processed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1714 +msgid "If the employee has taken annual leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1716 +msgid "" +"If all conditions are met, Odoo calculates the amount to be deducted from " +"the payroll to account for the holiday pay already received from the " +"previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1720 +msgid "Recovery of double holiday pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1722 +msgid "The recovery of double holiday pay follows these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1724 +msgid "" +"The system verifies the employee's contract and determines their employment " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1725 +msgid "The gross salary is calculated based on the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1726 +msgid "The number of months worked in the previous year is identified." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1727 +msgid "A threshold amount is computed as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1729 +msgid "" +"\\text{Threshold} = \\text{Current monthly salary} \\times \\text{Months worked in previous year}\n" +"\\times \\text{Occupation rate} \\times 7.67%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1735 +msgid "" +"If the amount on the holiday certificate from the previous employer is lower" +" than this threshold, no limit applies." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1738 +msgid "The system recovers the lower of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1740 +msgid "The calculated threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1741 +msgid "The actual amount paid by the previous employer." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1743 +msgid "" +"If the employee has worked for more than 12 months in the current company, " +"no double holiday pay needs to be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1747 +msgid "How to configure in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1749 +msgid "" +"In the employee form view, under the :guilabel:`Settings` tab, you can enter" +" the various amounts from holiday attests provided by the new employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Configuration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1755 +msgid "For simple holiday pay recovery, you need to enter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1757 +msgid "The :guilabel:`Number of days` for paid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1758 +msgid "The :guilabel:`Amount to recover` by the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1761 +msgid "" +"The :guilabel:`Recovered Amount` field displays the amount already " +"recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1763 +msgid "" +"For double holiday pay recovery, you must enter a **line for each employer's" +" holiday attest**. Each line should include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1766 +msgid "" +"The :guilabel:`# Months` (number of months) the employee worked for that " +"employer" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1767 +msgid "The :guilabel:`Amount` provided to the employee" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1768 +msgid "The :guilabel:`Occupational Rate`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1770 +msgid "" +"Odoo uses this data to compute a **recovery limit**. If the employee now has" +" a lower salary, the full amount cannot be recovered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1774 +msgid "" +"Be careful not to mix holiday attests for the current year (N) and the " +"previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1776 +msgid "" +"For simple holiday pay recovery, the system deducts the amount from each " +"legal time-off period until:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1779 +msgid "The **total amount** has been fully recovered, or" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1780 +msgid "" +"The **number of time-off days** has been matched (if the employee's current " +"salary is lower than before)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1786 +msgid "" +"Once the **payslip** is validated and paid, the recovered simple holiday pay" +" is reflected in the employee form view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Simple Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1792 +msgid "" +"On the double holiday payslip, click :guilabel:`Compute Double Pay Recovery`" +" to open a wizard that helps calculate the recoverable amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1795 +msgid "" +"In the :guilabel:`Double Pay Recovery Computation` wizard, you'll find:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1797 +msgid "" +"The relevant holiday attests listed in the :guilabel:`Occupation Lines`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1798 +msgid "The :guilabel:`Double Pay To Recover` amount based on the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1800 +msgid "This amount is **editable** if manual adjustments are needed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1805 +msgid "Once validated, the double pay recovery is applied to the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Holiday Pay Recovery Double Amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1810 +msgid "" +"Odoo automates the recovery of both **simple** and **double** holiday pay, " +"ensuring compliance with **Belgian labor laws**. By analyzing contract " +"details, employment duration, and past payments, Odoo calculates the " +"necessary deductions and prevents duplicate holiday pay payments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1817 +msgid "Individual accounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1820 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1973 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2132 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2316 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2842 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3064 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3134 +msgid "Introduction" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1822 +msgid "" +"The individual account provides workers with a detailed overview of their " +"earnings, deductions (such as social security contributions, withholding " +"tax, etc.), and the working days performed, on a pay period basis. " +"Additionally, it contains all relevant administrative data related to " +"remuneration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1828 +msgid "Required information in the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1830 +msgid "" +"The individual account must include several mandatory details as determined " +"by Royal Decree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1832 +msgid "**Employer identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1834 +msgid "Name, address, ONSS number, ONVA number" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1835 +msgid "Relevant joint committee (or sub-committee)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1836 +msgid "Name of the holiday fund for workers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1837 +msgid "Insurer for work-related accidents" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1838 +msgid "Approved social secretariat" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1839 +msgid "Relevant affiliation numbers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1841 +msgid "**Worker identification:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1843 +msgid "Name, address, date of birth, gender, tax status" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1844 +msgid "Type of employment contract, job title, professional qualification" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1845 +msgid "Workplace location (or note if working at multiple locations)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1846 +msgid "Start and end date of employment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1847 +msgid "Employee ID number, starting salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1848 +msgid "Remuneration components and payment periodicity" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1850 +msgid "**Remuneration components:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1852 +msgid "Per pay period (daily, weekly, bi-weekly, or monthly):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1854 +msgid "Number of working days and hours (regular, additional, and overtime)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1855 +msgid "" +"Days of work interruption and reasons (illness, vacations, public holidays, " +"replacement days, compensatory rest days, etc.)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1857 +msgid "" +"Fixed or hourly salary, variable remuneration, bonuses, meal vouchers, eco " +"vouchers, holiday pay (including early holiday pay if applicable), severance" +" pay, year-end bonuses (as per sectoral or other collective labor " +"agreements), benefits in kind and their estimated value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1860 +msgid "Gross amount of all remuneration components" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1861 +msgid "Amounts subject to social and tax deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1862 +msgid "" +"Various social and tax deductions: personal ONSS contributions, withholding " +"tax, special social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1864 +msgid "Net amount payable to the worker" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1865 +msgid "" +"Other payments made by the employer, including reimbursement of travel " +"expenses, allowances, and other payments" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1868 +msgid "Per quarter:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1870 +msgid "Number of actual working days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1871 +msgid "Days of work interruption by reason" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1872 +msgid "Total remuneration subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1873 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1878 +msgid "Employee social security contribution amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1875 +msgid "Per year:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1877 +msgid "Total amounts subject to social security contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1879 +msgid "Taxable remuneration and other amounts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1880 +msgid "Withholding tax amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1883 +msgid "Responsibility for establishing and updating the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1885 +msgid "" +"Belgian employers using **Odoo Payroll** can generate the individual " +"accounts of their workers." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1887 +msgid "However, to ensure accurate record-keeping, employers must:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1889 +msgid "Ensure payment of sector-mandated year-end bonuses" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1890 +msgid "" +"Ensure that all public holidays, legal vacation days, and compensatory rest " +"days are taken before the end of the year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1892 +msgid "Plan collective vacation and replacement public holidays in advance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1893 +msgid "" +"Pay workers their holiday pay (including early holiday pay if applicable)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1894 +msgid "Distribute due eco vouchers" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1895 +msgid "Pay any required travel expenses between home and work" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1897 +msgid "" +"If these obligations are met, the corresponding data will be included in the" +" individual account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1900 +msgid "Storage and retention period of the individual account" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1902 +msgid "" +"The individual account is a social document that must be kept by the " +"employer for a specified period after its creation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1905 +msgid "Employers may store individual accounts:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1907 +msgid "At the ONSS-registered address" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1908 +msgid "At a workplace" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1909 +msgid "" +"At their home or registered office if located in Belgium; otherwise, at the " +"residence of a designated agent in Belgium" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1911 +msgid "At the office of the approved social secretariat, if affiliated" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1913 +msgid "" +"Records must be kept legible and in a format allowing efficient oversight. " +"The retention period is **five years** from the end of the annual closing of" +" the account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1917 +msgid "When must workers receive a copy of their individual account?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1919 +msgid "Each worker must receive a copy of their individual account:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1921 +msgid "**During employment:** Before March 1 of the following year" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1922 +msgid "" +"**At the end of employment:** Within two months following the end of the " +"quarter in which the contract ended" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1924 +msgid "" +"**If additional payments occur after contract termination:** A copy " +"reflecting the additional payment must be provided within two months of the " +"payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1927 +msgid "" +"Additionally, employers must issue a **simplified individual account** with " +"certain worker and employer details within two months of the worker's " +"employment start date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1930 +msgid "" +"Any modifications to mandatory details, such as job function or workplace " +"location, must be communicated in writing (e.g., an updated simplified " +"individual account) within one month of the effective change date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1935 +msgid "Generate individual accounts in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1937 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> " +"Individual Accounts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1939 +msgid "" +"Then select the reference year and click the :guilabel:`Populate` button. " +"The :file:`.pdf` are displayed as soon as they are available and are " +"generated 30 by 30, this could take some time according to the number of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1943 +msgid "" +"On the first page, the :guilabel:`Employer Information` and the " +":guilabel:`Employee Information` is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1949 +msgid "" +"The next page displays all the employee worked days and payslip lines, month" +" by month, split by structure (e.g., End of year bonus and monthly pay)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Month by Month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1955 +msgid "" +"The next page displays the same information quarter by quarter and " +"summarized for the whole year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Individual Account PDF Quarter by Quarter." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1960 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3101 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3171 +msgid "" +"Once all PDF files are generated, they can be posted to the employee " +"documents portal if the **Documents** application is :doc:`installed and " +"properly configured <../../../productivity/documents>`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1964 +msgid "" +"Select the checkbox of each employee whose documents you want to post, and " +"click the :guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1970 +msgid "Intellectual property and 273 sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1975 +msgid "" +"The 273S declaration is used for the **Prepayment on Mobile Income (Pr.M)**," +" which concerns the taxation of **Author's Rights** and **Neighboring " +"Rights** (also known as **Revenus Mobilier**). These are specific types of " +"income that are subject to particular tax treatment in certain " +"jurisdictions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1980 +msgid "" +"This document provides users with essential information about how the 273S " +"declaration functions within Odoo for reporting income derived from these " +"rights, including applicable tax rates and conditions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1985 +msgid "Tax rates and calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1987 +msgid "" +"The net income from Author's Rights and Neighboring Rights is taxable at a " +"specific rate of **15%**. However, the effective tax rate can vary based on " +"the application of flat-rate deductions. These flat rates reduce the taxable" +" amount, leading to a lower effective tax rate for lower incomes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1991 +msgid "Key points of taxation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1993 +msgid "**Effective tax rate**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1995 +msgid "" +"For incomes below the first flat-rate threshold, the effective tax rate can " +"be as low as **7.5%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:1997 +msgid "" +"For incomes reaching the flat-rate ceiling of **37,500 EUR** (indexed " +"annually), the rate can increase to **12%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2000 +msgid "" +"**Additional taxes**: Income from Author's Rights and Neighboring Rights " +"must be declared in the personal income tax declaration. As a result, " +"municipal surcharges may also apply to the tax due." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2003 +msgid "" +"The **prepayment** of the tax is handled via a withholding tax on the " +"income. The debtor of the income (e.g., the employer or company paying the " +"royalties) must submit the 273S declaration to the tax authorities. This " +"withholding tax rate is generally **15%**, but for incomes exceeding the " +"indexed ceiling of **37,500 EUR**, the rate increases to **30%**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2009 +msgid "Benefits of Author's Rights in employment contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2011 +msgid "" +"Companies can offer tax-advantageous remuneration to their directors or " +"employees by granting **Author's Rights**. These rights are subject to a " +"**15% withholding tax**, but there are flat-rate deductions that make this " +"tax treatment very favorable, especially when incomes are lower." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2015 +msgid "Important considerations:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2017 +msgid "" +"**Creative works**: To qualify for Author's Rights protection, the work must" +" be creative, original, and fixed in a tangible form. Simple ideas or " +"concepts are not eligible." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2019 +msgid "" +"**Exploitation requirement**: From January 1, 2023, a new regulation " +"mandates that transferred or licensed protected works must be exploited, " +"meaning they must be used for public communication, execution, " +"representation, or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2022 +msgid "" +"**Eligibility for tax benefits**: To benefit from the favorable tax regime, " +"the rights holder must meet specific criteria, such as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2025 +msgid "Holding an \"Artistic Work Certificate.\"" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2026 +msgid "" +"Licensing or transferring rights to a third party for public communication " +"or reproduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2028 +msgid "" +"**Income ratio restrictions**: The proportion of income from Author's Rights" +" in relation to regular salary will be capped at **30%**, with **70%** of " +"the total income being subject to regular income tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2031 +msgid "" +"**Income cap**: The absolute ceiling for qualifying income under this regime" +" remains **37,500 EUR** (indexed at **70,220 EUR** for the 2024 income " +"year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2034 +msgid "" +"If your average income from the last four years exceeds this ceiling, you " +"will no longer be eligible for the advantageous tax regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2037 +msgid "" +"**Ruling Request**: For greater clarity on the scope and remuneration of the" +" transfer of Author's Rights, an advanced agreement with the tax authorities" +" (referred to as a **ruling**) can be requested." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2042 +msgid "Tax treatment of Author's Rights income" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2044 +msgid "" +"Since 2008, income from the transfer or licensing of Author's Rights has " +"benefited from a favorable tax treatment. Specifically, the income is " +"subject to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2047 +msgid "" +"**15% Withholding Tax** up to an indexed ceiling of **70,220 EUR** (2023 " +"income year)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2048 +msgid "**Flat-Rate Deductions**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2050 +msgid "" +"**50% flat-rate deduction** applies to the first **18,720 EUR** of income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2051 +msgid "" +"**25% flat-rate deduction** applies to the next **18,730 EUR** (from " +"**18,720 EUR to 37,450 EUR**)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2054 +msgid "Example of tax impact:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2056 +msgid "" +"For example, if a company director receives **10,000 EUR** in Author's " +"Rights income, they will pay **750 EUR** in tax (15% of the income after the" +" flat-rate deductions), leaving them with a net income of **9,250 EUR**. " +"This results in an effective tax rate of **7.5%** on the Author's Rights " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2062 +msgid "Odoo integration for Declaration 273S" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2064 +msgid "" +"Odoo users can efficiently manage the submission of the **273S Declaration**" +" for Author's Rights and Neighboring Rights income via the **Odoo Payroll** " +"module. Here's a quick overview of how this can be done:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2069 +msgid "Set up Author's Rights in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2071 +msgid "" +"On the employees form view, make sure the :guilabel:`Intellectual Property` " +"checkbox is enabled, and the allocated salary percentage is specified as " +"well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2074 +msgid "" +"Once a payslip is generated, the :abbr:`IP (intellectual property)` part is " +"computed based on the intellectual property percentage and the gross salary." +" The tax is computed accordingly based on the revenue amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 1." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Intellectual Property Payslip 2." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2085 +msgid "Generate the 273S form" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2087 +msgid "" +"Odoo can generate the 273S form automatically based on the income data " +"entered into the system. Ensure that all required details, including the " +"amount of income subject to the tax, are accurately entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2091 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> 273S " +"Sheet` to create a :guilabel:`New` record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2094 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, then click " +":guilabel:`Export XML file` to generate the declaration. Click " +":guilabel:`Export PDF File` to generate the printed details." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S Wizard File Generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2100 +msgid "" +"On the first PDF section, the company information and the global declaration" +" is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Company Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2105 +msgid "On the second section, the employees specific information is listed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "273S PDF Employee Info." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2111 +msgid "File the 273S Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2113 +msgid "" +"After generating the XML file, the company or the debtor of the income can " +"submit it to the tax authorities directly from MyMinfin. Keep track of the " +"filing and payment deadlines to ensure timely submission and compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2120 +msgid "" +"The **273S Declaration** is an essential tool for companies and individuals " +"benefiting from the favorable tax regime on Author's Rights and Neighboring " +"Rights. By leveraging Odoo's tax management features, users can ensure " +"compliance while optimizing their tax liabilities." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2124 +msgid "For further assistance, please consult a tax professional." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2129 +msgid "Representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2134 +msgid "" +"Representation fees must be **allocated on the payslip** between **serious " +"and non-serious representation costs**. By default, the threshold is set at " +"**€283.73**, but it can be adjusted based on what the company can **legally " +"justify**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2138 +msgid "" +"The representation fees is configured on the employee's contract form in the" +" :guilabel:`Expense Fees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2141 +msgid "" +"On the payslip, two or one line are displayed in the case the representation" +" fees amount exceeds the threshold or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2145 +msgid "Breakdown of the threshold" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2147 +msgid "" +"Only part of the representation costs are pro-rated because certain costs " +"are **fully covered** by the company. These fixed costs include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2150 +msgid "" +"\\text{€}283.73\\text{ Total} = \\begin{cases}\n" +"+ \\text{ €148.73 (Tax, since 2021 - coronavirus)} \\\\\n" +"+ \\text{ €30 (Internet)} \\\\\n" +"+ \\text{ €25 (Phone)} \\\\\n" +"+ \\text{ €80 (Car management fees)} \\\\\n" +"\\end{cases}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2160 +msgid "" +"The **serious portion** of the representation costs is **not prorated**, " +"while the **non-serious portion** is prorated based on working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2163 +msgid "" +"Navigate to :menuselection:`Payroll app --> Configuration --> Salary --> " +"Rule Parameters`, and search for the `CP200: Representation Fees Threshold` " +"record. Then, adapt the current value or introduce a new one from a given " +"date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Representation Fees Threshold." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2171 +msgid "" +"It is possible to define, based on job position, which jobs are eligible to " +"certain criteria in the :guilabel:`Payroll` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:0 +msgid "Representation Fees Job Position." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2178 +msgid "Calculation of representation fees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2181 +msgid "Conditions for payment" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2183 +msgid "Representation fees are only granted if:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2185 +msgid "The employee **receives a basic salary**, and" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2186 +msgid "" +"The employee has **worked at least part of the time**, unless a **salary " +"simulation** is in progress." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2189 +msgid "" +"If the employee is on **full leave** (without any working days), they are " +"**not eligible** for representation fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2193 +msgid "Determining the work time rate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2195 +msgid "" +"The number of **working days per week** is extracted from the employee's " +"contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2196 +msgid "" +"If the employee has periods of **incapacity for work** (e.g., illness), the " +"calculation adjusts the **work time rate** accordingly:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2199 +msgid "The total **incapacity hours** are determined." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2200 +msgid "" +"If the company follows a **biweekly schedule**, the incapacity hours are " +"divided by **two**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2201 +msgid "The incapacity **rate** is calculated as:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2203 +msgid "" +"\\text{incapacity rate} = 1 - \\frac{\\text{incapacity hours}}{\\text{total " +"weekly hours}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2208 +msgid "" +"The **final work time rate** is then adjusted by multiplying it with the " +"incapacity rate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2211 +msgid "Applying the threshold and pro-rating rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2213 +msgid "" +"The **default threshold (€283.73)** is applied unless adjusted by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2214 +msgid "" +"If the employee has **worked a full-time schedule**, they receive the **full" +" representation fees** without reduction." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2216 +msgid "" +"If the employee works **part-time** (contractual or due to time credit), " +"only the **non-serious portion** of the fees is prorated." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2219 +msgid "The prorated formula for non-serious expenses is:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2221 +msgid "" +"\\text{adjusted amount} = \\text{threshold} + (\\text{total fees} - \\text{threshold}) \\times\n" +"\\frac{\\text{work time rate}}{100}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2227 +msgid "" +"If the employee has **missing workdays**, the final amount is further " +"adjusted:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2229 +msgid "First calculate the **daily reduction**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2231 +msgid "" +"\\text{daily reduction} = \\frac{(\\text{total amount} - \\text{threshold}) " +"\\times 3}{13 \\times \\text{days per week}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2236 +msgid "Then calculate the **final amount**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2238 +msgid "" +"\\text{final amount} = max(0, \\text{total amount} - \\text{daily reduction} \\times\n" +"\\text{missing days})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2245 +msgid "Final calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2247 +msgid "" +"If the employee meets all conditions, the final representation fees amount " +"is **rounded to two decimal places** for payroll purposes." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2249 +msgid "" +"Employees working a full schedule receive **full reimbursement**, while " +"those working **reduced hours** have the **non-serious portion prorated** " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2255 +msgid "" +"This calculation ensures **fair allocation** of representation fees by " +"distinguishing between **fixed serious costs** and **prorated non-serious " +"costs**. The company can adjust the **threshold (€283.73 by default)** based" +" on **justifiable business expenses**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2259 +msgid "" +"Employees working **full-time** receive their full representation fees, " +"while those working **part-time or with absences** only receive a **pro-" +"rated portion** of the non-serious fees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2265 +msgid "Sick time off and relapse" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2267 +msgid "In Belgium, sick leave is managed according to two main regimes:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2269 +msgid "" +"**With guaranteed salary**: The employer continues to pay the worker's " +"salary for a specified period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2271 +msgid "" +"**Without guaranteed salary**: The worker receives benefits from the mutual " +"insurance company after the guaranteed salary period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2275 +msgid "Sick leave with guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2277 +msgid "" +"The guaranteed salary is a period during which the employer continues to pay" +" the salary of the worker who is unable to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2280 +msgid "" +"**Employees**: The employer pays 100% of the salary during the first full " +"month of incapacity. After this period, if the incapacity continues, the " +"worker falls under the mutual insurance regime." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2284 +msgid "Sick leave without guaranteed salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2286 +msgid "" +"After the guaranteed salary period, the ONEM (National Employment Office) or" +" the mutual insurance company takes over." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2289 +msgid "" +"**Long-term illness**: An incapacity lasting more than 30 days leads to " +"benefits from the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2291 +msgid "" +"**Relapse**: If a worker returns to work and then becomes ill again for the " +"same reason within 14 days, this may be considered a relapse, and the rules " +"for guaranteed salary may be adjusted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2295 +msgid "Management in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2297 +msgid "" +"In Odoo, sick leave is automatically managed if the absences are related to " +"the *Sick Time Off* work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2300 +msgid "" +"**Recording time off**: The employee records their absence through the " +"**Time Off** module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2301 +msgid "" +"**Automation of work entries**: If the request is approved, Odoo " +"automatically generates the corresponding Work Entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2303 +msgid "" +"**Impact on payroll**: The guaranteed salary is automatically calculated " +"according to the rules configured based on the worker's status (employee)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2305 +msgid "" +"**Compensation after the guaranteed salary**: Once the guaranteed salary " +"period has expired, Odoo adjusts the Work Entries to reflect the transition " +"to the mutual insurance company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2308 +msgid "" +"Thus, Odoo ensures a smooth and compliant management of sick leave according" +" to Belgian regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2313 +msgid "Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2318 +msgid "" +"The *Social Balance Sheet* was introduced by the law of December 22, 1995, " +"as part of measures for the implementation of the multi-year employment " +"plan. Companies required to file annual accounts (including some that are " +"not obligated to publish such accounts - see the `National Bank of Belgium " +"website `_ for details) must also prepare and submit a " +"Social Balance Sheet to the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2324 +msgid "" +"The Royal Decree of August 4, 1996, incorporates the Social Balance Sheet " +"into the annual accounts, specifically as an annex. This makes it an " +"integral part of a company's financial statements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2328 +msgid "Contents of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2330 +msgid "" +"The content of the Social Balance Sheet is determined by the Royal Decree of" +" January 30, 2001, implementing the Company Code. The Social Balance Sheet " +"consists of several sections:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2333 +msgid "" +"Sections I and II: Information on employed persons and personnel movements " +"during the fiscal year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2334 +msgid "Section III: Initiatives related to training." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2336 +msgid "" +"Since the Social Balance Sheet is part of a company's annual accounts, the " +"works council receives this information as part of its mission regarding " +"economic and financial information." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2339 +msgid "" +"Additionally, the works council receives data on employment-related benefits" +" along with annual employment-related information (Trillium). These details " +"were fully integrated into the Social Balance Sheet until 2008." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2344 +msgid "Scope of the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2346 +msgid "" +"The Social Balance Sheet contains specific data related to workforce " +"composition, staff turnover, and training programs. Some organizations not " +"required to publish annual accounts must still file a separate Social " +"Balance Sheet. This applies primarily to certain hospitals and private legal" +" entities employing at least 20 full-time equivalents (FTEs)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2351 +msgid "" +"Any company, association, or foundation with at least 20 workers on an " +"annual average (in FTE) must complete and submit the Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2354 +msgid "The Social Balance Sheet is part of:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2356 +msgid "" +"\"Other documents to be filed under the Company and Associations Code\" (for" +" companies);" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2357 +msgid "\"Explanatory Notes\" (for associations and foundations)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2360 +msgid "Obligations by entity type" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2363 +msgid "" +"Companies, associations, and foundations required to publish a Social " +"Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2365 +msgid "For Belgian companies employing at least one FTE:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2367 +msgid "" +"**Standardized model**: This schema includes a \"Social Balance Sheet\" " +"section, which must be completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2369 +msgid "" +"**Specific model**: If the model used does not include a Social Balance " +"Sheet, it must be provided separately." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2372 +msgid "For Belgian associations and foundations employing at least 20 FTEs:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2374 +msgid "" +"**Standard model**: Includes a \"Social Balance Sheet\" section that must be" +" completed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2375 +msgid "" +"**Specific model**: A separate Social Balance Sheet must be submitted if the" +" chosen model does not include one." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2378 +msgid "" +"Associations and foundations with fewer than 20 FTEs may voluntarily " +"complete the Social Balance Sheet but are not legally required to do so." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2381 +msgid "" +"For foreign companies, such as branches of foreign corporations and foreign " +"non-profit organizations (ASBL) with activities in Belgium, the Social " +"Balance Sheet applies only to their Belgian operations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2385 +msgid "" +"The Social Balance Sheet is made publicly available by the Central Balance " +"Sheet Office as part of the financial statements submission." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2389 +msgid "Entities required to file a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2391 +msgid "" +"Certain organizations that do not need to publish annual accounts must still" +" submit a Social Balance Sheet to the Central Balance Sheet Office. This " +"data is used exclusively for statistical purposes and is not made publicly " +"available. Submission in these cases is free of charge." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2395 +msgid "This exception applies to:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2397 +msgid "" +"**Hospitals**, unless they are structured as limited liability companies or " +"large ASBLs, which must submit full financial statements, including the " +"integrated Social Balance Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2399 +msgid "" +"**Private legal entities** that are not required to submit annual accounts " +"but have at least 20 employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2402 +msgid "The required model depends on the entity type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2404 +msgid "" +"**Hospitals** must use the full or abridged Social Balance Sheet model based" +" on their size." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2405 +msgid "" +"**Foreign entities** must use the full or abridged Social Balance Sheet " +"model, based on the size of their Belgian establishments." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2407 +msgid "" +"**Private legal entities** with at least 50 employees must use the full " +"model, while those with 20-49 employees may use the abridged model." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2411 +msgid "Social Balance Sheet models" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2413 +msgid "" +"The latest versions of the Social Balance Sheet models can be found at the " +"following links:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2415 +msgid "**Full Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2417 +msgid "" +"PDF: `Full Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2418 +msgid "" +"Word: `Full Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2420 +msgid "**Abridged Model**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2422 +msgid "" +"PDF: `Abridged Social Balance Sheet PDF " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2423 +msgid "" +"Word: `Abridged Social Balance Sheet Word " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2426 +msgid "Assistance in completing the Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2428 +msgid "" +"For guidance on completing the Social Balance Sheet, refer to the following " +"resources:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2430 +msgid "" +"**CNC Opinion S100**: `Questions and Answers on the Social Balance Sheet " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2431 +msgid "" +"**CNC Opinion 2009/12**: `Social Balance Sheet and Statutory Workers " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2432 +msgid "" +"**Explanatory Note**: `Information on Training Activities " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2435 +msgid "Submitting a separate Social Balance Sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2437 +msgid "" +"A separate Social Balance Sheet must be submitted online as a PDF via the " +"**Filing** application. The model can be selected under :guilabel:`Other " +"Documents`, with options for :guilabel:`Abridged Social Balance Sheet` or " +":guilabel:`Full Social Balance Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2441 +msgid "" +"For further details, visit the National Bank of Belgium's website: " +"`www.nbb.be `_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2444 +msgid "Generating Social Balance Sheet in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2446 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Balance Sheet` and select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2452 +msgid "" +"Then click :guilabel:`Export to PDF` or :guilabel:`Export to XLSX` to " +"generate the social balance sheets containing all the data available in your" +" Odoo database." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2455 +msgid "" +"The different pieces of information are split by gender, or by working " +"schedule (Part Time, Full Time, Full Time equivalent), for the whole period," +" and month by month, as requested by the National Bank of Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Balance Sheet XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2471 +msgid "Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2473 +msgid "" +"The Social Security certificate in Odoo provides a detailed breakdown of all" +" social charges paid by the employee or employer, categorized by type (e.g.," +" year-end bonus, private car reimbursement, double holiday pay, etc.). This " +"report is particularly useful for audit companies and for verifying that the" +" declared amounts align with accounting entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2479 +msgid "Accessing the Social Security certificate" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2481 +msgid "To generate the Social Security certificate, follow these steps:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2483 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> Belgium --> Social" +" Security Certificate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2485 +msgid "Select the reference :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2486 +msgid "Choose the data :guilabel:`Aggregation Level`:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2488 +msgid ":guilabel:`Whole Company`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2489 +msgid ":guilabel:`By Department`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2490 +msgid ":guilabel:`By Employee`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2496 +msgid "Exporting the report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2498 +msgid "" +"Once the selections are made, you can export the report in different " +"formats:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2500 +msgid "" +"Click :guilabel:`Export to PDF` to generate a printable version of the " +"Social Security certificate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2502 +msgid "" +"Click :guilabel:`Export to XLSX` to generate an Excel file containing all " +"relevant data." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Header." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate PDF Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Social Security Certificate XLSX Content." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2513 +msgid "" +"This feature ensures full transparency and compliance with social security " +"regulations in Belgium." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2523 +msgid "Legal time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2525 +msgid "" +"This guide provides an overview of the basic rules governing legal holiday " +"entitlements in Belgium for employers using Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2529 +msgid "Holiday entitlement calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2531 +msgid "" +"Your holiday entitlement for the current year (N) is determined by the " +"number of months worked in Belgium during the previous year (N-1)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2534 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2565 +msgid "**Calculation details:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2536 +msgid "" +"Employees earn **2 days of leave per month** based on a 6-day work week." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2537 +msgid "" +"The entitlement is adjusted for a 5-day work week: :math:`(\\text{Total " +"Days} \\div 6) \\times 5`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2540 +msgid "If an employee worked **7 months** in the previous year (N-1):" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2542 +msgid "**6-day work week:** :math:`7 \\times 2 = 14 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2543 +msgid "**5-day work week:** :math:`14 \\div 6 \\times 5 = 11.67 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2545 +msgid "**Partial Month Calculation:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2547 +msgid "Worked **1st to 10th**: Full month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2548 +msgid "Worked **11th to 19th**: Half month counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2549 +msgid "Worked **20th onwards**: Month not counted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2551 +msgid "**Rounding Rules:**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2553 +msgid "Less than **0.35**: Round to **0**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2554 +msgid "Between **0.35 - 0.74**: Round to **0.5**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2555 +msgid "**0.75 and above**: Round to **1**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2557 +msgid "" +"For a full-time employee, this typically results in **11.5 days of legal " +"holiday** entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2560 +msgid "Maximum holiday entitlement" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2562 +msgid "" +"Employees are entitled to a maximum of **4 weeks** of holiday based on their" +" working schedule. If an employee switches between full-time and part-time " +"work, their entitlement is adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2567 +msgid "**5-day work week**: :math:`4 \\times 5 = 20 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2568 +msgid "**4-day work week**: :math:`4 \\times 4 = 16 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2569 +msgid "**3-day work week**: :math:`4 \\times 3 = 12 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2572 +msgid "" +"If an employee joined **Odoo on January 1, 2024**, and plans to switch to a " +"**3-day work week from April 1, 2024**:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2575 +msgid "**Step 1: Calculate holiday entitlement for 2024**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2577 +msgid "The employee worked **9 months in 2023**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2578 +msgid "**6-day work week basis**: :math:`9 \\times 2 = 18 \\text{ days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2579 +msgid "" +"Adjusted for **5-day work week**: :math:`18 \\div 6 \\times 5 = 15 \\text{ " +"days}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2581 +msgid "**Step 2: Verify maximum holiday entitlement**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2583 +msgid "For a **5-day work week**, the maximum entitlement is **20 days**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2584 +msgid "" +"Since the employee is entitled to **15 days**, they remain within the limit." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2586 +msgid "**Step 3: Adjust entitlement for the new work schedule**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2588 +msgid "From April 1, 2024, the employee moves to a **3-day work week**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2589 +msgid "" +"Maximum entitlement for a **3-day work week**: :math:`3 \\times 4 = 12 " +"\\text{ days}`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2590 +msgid "" +"If no leave is taken before April 1, the employee may take up to **12 days**" +" from their 15-day entitlement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2592 +msgid "The **remaining 3 days** will be settled at the end of the year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2594 +msgid "" +"This ensures compliance with Belgian legal leave regulations and allows " +"employers to manage holiday entitlements effectively within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2598 +msgid "Legal time off allocation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2600 +msgid "" +"This is possible to generate the legal time off for all your employees at " +"the beginning of a new year using the wizard in :menuselection:`Payroll app " +"--> Reporting --> Belgium --> Paid Time Off Allocation`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2604 +msgid "" +"Based on your employees occupation over last year, the number of available " +"time off is pre-computed for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocation Wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2610 +msgid "" +"Once validated, a draft allocation is generated for each single employee, " +"waiting a manual confirmation that can be done in batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Paid Time Off Allocations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2619 +msgid "European time off" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2622 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2854 +msgid "How does it work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2624 +msgid "" +"If you were not subject to Belgian ONSS contributions before joining our " +"company and do not have entitlement to legal holidays, or if your " +"entitlement is incomplete, you can apply for European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2628 +msgid "" +"To qualify for European leave in a given year, you must work for at least 3 " +"months during that year, whether with us or another employer. Once you have " +"met this requirement, you will earn 5 days of European leave. Subsequently, " +"you will accumulate additional days of vacation each month as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2632 +msgid "After 3 months: 5 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2633 +msgid "After 4 months: 7 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2634 +msgid "After 5 months: 9 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2635 +msgid "After 6 months: 10 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2636 +msgid "After 7 months: 12 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2637 +msgid "After 8 months: 14 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2638 +msgid "After 9 months: 15 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2639 +msgid "After 10 months: 17 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2640 +msgid "After 11 months: 19 days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2643 +msgid "" +"The total of legal leave and European leave cannot exceed 20 days per year. " +"You must use all your legal holidays before taking European leave." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2646 +msgid "" +"European leave entitlement expires on December 31st of the year it is earned" +" and cannot be carried over to the following year. To qualify for European " +"leave in a new year, you must complete another 3 months of work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2651 +msgid "How are these days paid?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2653 +msgid "" +"European leaves are paid holidays taken in advance of your \"Double Holiday " +"Pay\" (the June extra pay) for the following year. Essentially, the more " +"European leave days you take in a given year, the less you will receive as " +"June extra pay in the following year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2660 +msgid "Working schedule change" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2662 +msgid "" +"This guide explains how to modify an employee's working time schedule in the" +" Belgian payroll module of Odoo. Changing an employee's working hours " +"affects their wage calculation, time-off allocation, and contract terms." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2667 +msgid "Steps to change an employee's working schedule" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2669 +msgid "" +"Navigate to the employee's contract (:menuselection:`Payroll app --> " +"Contracts`), and select the contract of the employee whose working schedule " +"you want to modify." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2671 +msgid "" +"Click on :icon:`fa-cog` :guilabel:`(Action)` and select :guilabel:`Working " +"Schedule Change`. The wizard displays the current contract details and " +"allows you to set new working time parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2673 +msgid "Set the new working schedule:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2675 +msgid "" +"Choose the new :guilabel:`Working Schedule` from the available resource " +"calendars." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2676 +msgid "Define the :guilabel:`Start Date` for the change (mandatory)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2677 +msgid "If applicable, specify an :guilabel:`End Date`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2678 +msgid "" +"If the :guilabel:`Part Time` checkbox is selected, any difference between " +"the reference calendar and the employee's new calendar will be covered using" +" the *Absence Work Entry Type*. This ensures that the employee's monthly " +"salary remains the same, regardless of the number of absence days in a given" +" month. This setup is required for configuring *Time Credit*, *Parental " +"Leave*, or *Medical Half-Time* correctly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2684 +msgid "Adjust the employee's wage:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2686 +msgid "" +"The wizard automatically computes the full-time equivalent wage based on the" +" new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2688 +msgid "You can review and modify the new wage if necessary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2690 +msgid "Manage time off allocation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2692 +msgid "Select the relevant :guilabel:`Time Off Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2693 +msgid "" +"Odoo automatically adjusts the employee's time-off entitlement based on the " +"new working schedule using the following formula:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2696 +msgid "" +"\\text{New Time Off Allocation} = \\max(\\min(\\text{ Computed Allocation},\n" +"\\text{ Max Allocation}) + \\text{ Leaves Taken}, \\text{ Leaves Taken})" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2702 +msgid "" +"**Computed Allocation** is the expected leave allocation based on the new " +"schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2703 +msgid "" +"**Max Allocation** is the maximum number of days allowed under the new " +"working time." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2704 +msgid "" +"**Leaves Taken** ensures the employee does not receive fewer days than " +"already used." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2706 +msgid "Decide on a follow-up contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2708 +msgid "" +"If the working time change is temporary, you can enable :guilabel:`Post " +"Change Contract Creation` to automatically create a contract that resumes " +"the previous working schedule after the specified end date." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2712 +msgid "Validate the changes" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2714 +msgid "Click :guilabel:`Validate` to apply the new working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2715 +msgid "" +"If the new schedule is the same as the current one, an error will be " +"displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2716 +msgid "" +"The system will create a new contract with the updated working time and " +"wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2717 +msgid "" +"If a previous contract existed, it will be closed with an end date before " +"the new contract begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2721 +msgid "Result" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2723 +msgid "The employee's new working schedule is recorded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2724 +msgid "Wage and time-off entitlements are adjusted accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2725 +msgid "A follow-up contract is created if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "Working Schedule Change New Contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2733 +msgid "Work entries exports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2736 +msgid "What are work entries?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2738 +msgid "" +"In the context of payroll, *work entries* typically refer to records or " +"documentation related to an employee's work hours and earnings for a " +"specific pay period. These entries are crucial for accurately calculating " +"and processing employee compensation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2742 +msgid "" +"Work entries in the context of payroll are essential for both employees and " +"employers. They provide a transparent and accurate record of an employee's " +"compensation and deductions, ensuring that employees are paid correctly and " +"that tax and legal requirements are met. Payroll software and systems are " +"commonly used to manage and automate these work entries, making the payroll " +"process more efficient and accurate." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2749 +msgid "Main concepts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2752 +msgid "General" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2754 +msgid "" +"In Odoo, work entries mainly refer to *time entries* (attendance tracking), " +"these are work entries that consist of time records, which include the " +"number of hours worked by an employee during a given pay period. These " +"entries may specify regular working hours, overtime hours, and any other " +"relevant time-related information, such as breaks, paid time off, unpaid " +"time off, parental leave, credit-time, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2760 +msgid "" +"Work entries serve a dual role in payroll management. First, they enable " +"organizations to independently compute employee payslips. Second, they " +"facilitate the transmission of pertinent data to external payroll service " +"providers, who then use this information to calculate and generate the " +"payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2768 +msgid "" +"They have a Name: used to identify the type of entry (e.g., Attendance, Paid" +" Time Off, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2769 +msgid "They have a Payroll Code: used in Odoo's salary rules computations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2770 +msgid "" +"They have an External Code: used to provide the correct Work Entry code to " +"an external payroll service provider." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2772 +msgid "" +"They are generated based on the configuration of the contract and the time " +"off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2773 +msgid "" +"They have a duration, a start and end date, a state and are always linked to" +" an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2778 +msgid "" +"They are the main source of configuration for your work entries. Thanks to " +"your different types of work entries, you'll be able to differentiate the " +"time records of your employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2780 +msgid "They have a name." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2781 +msgid "" +"They contain a code, external code, payroll code and a color for visual " +"tracking." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2782 +msgid "" +"They allow other types of configurations such as how they are displayed in " +"payslips, decide whether this type of work entry should be considered as " +"paid or unpaid (eg. unpaid leave), decide whether this type of work entry " +"has a link with time off, is valid for some advantages or how it should be " +"reflected in your reporting." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2788 +#: ../../content/applications/hr/time_off.rst:42 +msgid "Time off types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2790 +msgid "" +"As mentioned above, since work entry types can be linked to a time off type," +" you are also able to define the work entry type for each time-off type. On " +"the time off type you have a many2one relation with the work entry type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2795 +msgid "Steps to generate the work entries of your staff" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2797 +msgid "Create all the employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2798 +msgid "" +"Create a contract and set its status to :guilabel:`Running` for each " +"employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2800 +msgid "" +"In the contract, choose the :guilabel:`Work Entry Source`. It tells the " +"system how work entries for an employee should be generated. It can be based" +" on:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2803 +msgid "" +":guilabel:`Working Schedule`: Odoo uses the predefined working hours and " +"days set in the employee's working schedule to generate work entries. This " +"is useful for regular, predictable shifts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2806 +msgid "" +":guilabel:`Attendances`: Work entries are generated from the employee's " +"attendance records (i.e., when they check-in and check-out)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2808 +msgid "" +":guilabel:`Planning`: Work entries are created based on the validated shifts" +" or slots allocated to the employee in the **Planning** app (often used for " +"scheduling roles like retail shifts, restaurants, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2812 +msgid "Generate the work entries each month" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2814 +msgid "" +"Odoo automatically creates the work entries in the **Payroll** app based on " +"the work entry source of the contract and the different time-offs taken. You" +" can edit the work entries manually. You can always decide to regenerate " +"work entries manually but be careful if you already made some manual " +"changes, Odoo will regenerate the work entries based on what it knows (e.g.," +" your working schedule and time off)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2819 +msgid "Managing conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2821 +msgid "" +"Conflicts are pointing to entries that can't be validated without your " +"intervention. This means you'll have to qualify the entry and decide which " +"is the correct entry to be defined for the time period if you want to be " +"able to generate the payslip or validate the entries. Conflicts arise when " +"there are overlapping entries or when Odoo detects that there is a time off " +"request still pending for validation. For instance, if an employee is marked" +" as attending work and at the same time there's a paid leave request to be " +"validated for the same period, that's a conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2828 +msgid "" +"Conflicts can be managed by filtering on the conflicting entries and " +"resolving the discrepancy. Since **Odoo 16.4**, Odoo filters by default on " +"conflicting entries. For prior versions, you can still filter manually on " +"conflicting entries or use the conflicting menu item." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2831 +msgid "" +"Once the conflict is resolved you can either proceed to generate the " +"payslips for your employees or export your work entries to the right entity." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2835 +msgid "Export work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2838 +msgid "" +"This section is about exporting work entries to SD Worx, but the " +"configuration and behavior is similar for other exports to Partena, Group S " +"and UCM." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2844 +msgid "" +"This sheet is here to help you learn how Odoo's **SD Worx** " +"(`l10n_be_hr_payroll_sd_worx`) module simplifies payroll by enabling easy " +"export of work entries. This guide provides quick steps to generate " +":file:`.txt` files for direct import into SD Worx calendars, saving time and" +" ensuring accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2849 +msgid "" +"First and foremost, it's important to understand there is no direct " +"integration between Odoo and SD Worx. There is no automatic exchange of " +"information, either way. Odoo does not communicate directly with SD Worx, " +"and the reverse is also true." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2856 +msgid "" +"In reality, Odoo provides a standardized export in .txt format for " +"employees' work entries, allowing the generation of a file that conforms to " +"a specific format for inputting these entries into the SD Worx software." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2861 +msgid "What does it mean in terms of data management?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2863 +msgid "" +"Since there is no direct integration between both systems, it implies that " +"certain data will need to be manually entered into both systems. For " +"instance, when you create a new employee in Odoo, you'll also need to " +"manually create the employee in SD Worx (and vice versa). This manual data " +"entry requirement extends to various aspects such as contracts, work " +"schedules, salary details, and personal information about employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2869 +msgid "" +"Essentially, all the information necessary for SD Worx to calculate salaries" +" and generate payslips must be manually inputted into both systems." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2873 +msgid "What's the advantage of exporting to SD worx?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2875 +msgid "" +"Odoo is an integrated software that can comprehensively handle all variable " +"payroll elements, including employee personal information, contract details," +" various time-off types, and other work entry categories. Through Odoo's " +"integration capabilities, you can access all this crucial data in one " +"centralized location, making it easily accessible for your HR team and " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2880 +msgid "" +"This integration not only ensures data accuracy but also maintains " +"consistency, reducing the likelihood of errors when transmitting work entry " +"information to your external payroll provider. With the module in place, a " +"single click generates a :file:`.txt` file that's ready for direct import " +"into SD Worx, streamlining the entire data transmission process." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2886 +msgid "Steps to set up the SD Worx module" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2889 +msgid "" +"You must be logged into a Belgian company for the following steps to work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2891 +msgid "" +":ref:`install ` the **Belgium - Payroll - Export to SD " +"Worx** (`l10n_be_hr_payroll_sd_worx`) module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2893 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Settings` to fill in" +" the :guilabel:`SD Worx code` field. This is the company's SD Worx code, you" +" get it directly from the SD worx software. When you create a company, it " +"has a unique identifier which you need to set in the field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2897 +msgid "" +"For each employee, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2898 +msgid "" +"For work entry types, under the :guilabel:`Settings` tab, fill in the " +":guilabel:`SDWorx code` field as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2901 +msgid "" +"You can now export your work entries in the SD Worx :file:`.txt` format by " +"opening the wizard under :menuselection:`Payroll app --> Reporting --> " +"Belgium --> Export Work Entries to SDWorx`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2904 +msgid "" +"The file contains a series of lines such as the following line of text: " +"`1111110000024K2023042370100360`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2907 +msgid "" +"Each line represents a work entry, and the structure is outlined below:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2909 +msgid "`111111` -> Company SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2910 +msgid "`0000024` -> Employee SD Worx code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2911 +msgid "`K` -> Delimiter" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2912 +msgid "`20230423` -> Date" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2913 +msgid "`7010` -> SD Worx work entry code" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2914 +msgid "`0360` -> Duration (edited)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2916 +msgid "" +"Once the :file:`.txt` file is exported, it can be directly imported in this " +"format into the SD Worx software. Doing so updates the calendars of each " +"collaborator." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2922 +msgid "274.XX sheets" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2924 +msgid "" +"This section provides an overview of Declaration 274, its components, and " +"how it is handled within Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2928 +msgid "Declaration 274.10" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2930 +msgid "" +"Withholding tax is an advance payment on professional income tax. It is " +"calculated based on guidelines established by the tax administration. While " +"reducing withholding tax is generally not allowed, employees may request to " +"pay more in order to better match their final tax liability." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2934 +msgid "" +"Withholding tax must be deducted from both employees' and company directors'" +" income. If the withholding tax is insufficient, advance tax payments must " +"be made to avoid additional tax penalties." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2938 +msgid "" +"In practice, some employees do not inform their employer of personal changes" +" (e.g., having a child), which can affect tax calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2941 +msgid "" +"Withholding tax must be declared and paid either quarterly or monthly using " +"form 274. These declarations must be submitted via the FINPROF application " +"by the 15th of the month following the reporting period." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2945 +msgid "" +"Taxable income and corresponding withholding tax must be recorded in fiscal " +"remuneration forms 281.x and summary statements 325x. Employers failing to " +"report these correctly may be subject to a 309% penalty on undisclosed " +"amounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2949 +msgid "" +"The tax administration compares the declared amounts in form 274 with the " +"amounts reported in the fiscal forms. If withholding tax payments are " +"insufficient, the company may be charged the difference. If a 274 form is " +"submitted without corresponding tax payment, additional tax penalties will " +"apply." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2954 +msgid "" +"It is crucial to adhere to all administrative guidelines to avoid unexpected" +" tax charges." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2957 +msgid "Declarations 274.32, 274.33, 274.34" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2960 +msgid "Withholding tax exemptions for research employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2962 +msgid "" +"Companies employing scientific researchers may qualify for withholding tax " +"reductions under specific conditions:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2965 +msgid "**Form 281.32** applies to civil engineers and PhD holders." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2966 +msgid "**Form 281.33** applies to employees holding a master's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2967 +msgid "**Form 281.34** applies to employees holding a bachelor's degree." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2969 +msgid "" +"Employers engaged in scientific research may be eligible for an exemption " +"from withholding tax payments. To qualify, they must register their R&D " +"projects with Belspo. From August 1, 2023, this registration must occur " +"before the project begins." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2974 +msgid "Tax exemption details" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2976 +msgid "" +"This tax incentive allows companies to retain 80% of the withholding tax " +"deducted from researchers' salaries. However, the exemption rate differs for" +" researchers based on their qualifications:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2979 +msgid "PhD and master's degree holders: Full 80% exemption." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2980 +msgid "Bachelor's degree holders: 50% of the full exemption amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2981 +msgid "For non-SME companies, this limit is further reduced to 25%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2983 +msgid "" +"The exemption applies only to the portion of working time dedicated to " +"scientific research, covering fundamental research, industrial research, or " +"experimental development." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2986 +msgid "This exemption does not affect the net salary of employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2989 +msgid "Capping rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2991 +msgid "" +"The total exemption granted to researchers with a bachelor's degree is " +"limited to 25% of the exemption granted to PhD and master's degree holders. " +"For small companies (as defined in Article 15 §§ 1-6 of the Companies Code)," +" this limit is doubled. These rules have remained unchanged since January 1," +" 2020." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2997 +msgid "How it works in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:2999 +msgid "" +"Odoo automates the calculation and declaration of withholding tax exemptions" +" using predefined payroll structures. Below is an explanation of how the " +"system processes these exemptions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3002 +msgid "" +"Navigate to :menuselection:`Payroll app --> Reporting --> 274.XX Sheets` to " +"create a new declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3005 +msgid "" +"Select the reference :guilabel:`Year` and :guilabel:`Month`, and the " +"different amounts are computed accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3008 +msgid "**Payroll calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3010 +msgid "Odoo calculates gross salary and total withholding tax." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3011 +msgid "" +"It accounts for specific payroll components, including December double " +"bonuses." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3013 +msgid "**Filtering eligible payslips**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3015 +msgid "Payslips linked to research-related contracts are considered." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3016 +msgid "" +"Employees are categorized based on their qualifications (PhD, master's, or " +"bachelor's degrees)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3018 +msgid "**Exemption calculation**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3020 +msgid "" +"The withholding tax exemption is calculated at 80% of the withheld amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3021 +msgid "" +"Exemptions for bachelor's degree holders are capped according to " +"regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3023 +msgid "**Final adjustments**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3025 +msgid "The system ensures compliance with legal capping rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3026 +msgid "" +"If necessary, adjustments are made based on the total exemption granted." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3028 +msgid "" +"Click on :guilabel:`Export XML file` to generate the file to post on FINPROF" +" portal and the structured communication to link to your payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:-1 +msgid "274.XX XML file." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3034 +msgid "" +"Click on :guilabel:`Create 274.XX Sheets` to generate the :file:`.pdf` files" +" of those declarations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3037 +msgid "" +"In order to for the exemption to work properly, the *Certificate Level* " +"should be correctly configured on the employee's form." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3040 +msgid "" +"The *Time Percentage R&D* rate should be specified on the employee's " +"contract form as well." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3042 +msgid "" +"If the accounting application is installed and running properly, you can " +"also post directly the different amounts in your accounting entries with the" +" :guilabel:`Post Journal Entries` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3046 +msgid "" +"If the *Post Journal Entries* is not present on the wizard, you need to " +"configure the journal and the different accounts for each amount type from " +":menuselection:`Payroll app --> Configuration --> Settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3050 +msgid "" +"In the :guilabel:`Belgian Localization` section, complete each of the " +":guilabel:`Witholding Taxes Exemption` journal entry accounts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3053 +msgid "" +"Employers using Odoo can efficiently manage and report withholding tax " +"exemptions, ensuring compliance with regulatory requirements." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3056 +msgid "" +"For further details, consult the Odoo finance documentation or your tax " +"adviser." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3061 +msgid "281.10 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3066 +msgid "" +"The Belgian fiscal declaration 281.10 is an annual statement that employers " +"must submit to the tax authorities, detailing the salaries and benefits " +"provided to each employee. This declaration ensures accurate tax " +"calculations and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3071 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3141 +msgid "Generating the declaration in Odoo" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3073 +msgid "" +"Odoo provides a streamlined process for generating the 281.10 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3077 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3147 +msgid "Global XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3079 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.10 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3082 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3152 +msgid "Then, create a new record by selecting the reference :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3085 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3155 +msgid "" +"The :guilabel:`Sending Type` and :guilabel:`Treatment Type` options are " +"currently experimental and should be kept at their default values to ensure " +"a valid original declaration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3088 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3158 +msgid "" +"Click the :guilabel:`Populate` button to generate the eligible employees, " +"then click the :guilabel:`Create XML` button. A green indicator will appear " +"to confirm successful file generation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3092 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3162 +msgid "Individual PDF declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3094 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3164 +msgid "" +"To generate individual PDF files for each employee, click the " +":guilabel:`Populate` button. A line is generated for each employee who " +"received a payslip during the reference year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3098 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3168 +msgid "" +"The PDF files are generated automatically in batches of 30, so the process " +"may take some time to complete." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3105 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3175 +msgid "" +"Select the employees whose documents you want to post, then click the " +":guilabel:`Post PDF` button." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3107 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3177 +msgid "" +"Once posted, employees can access the PDF from their documents portal via " +"the :icon:`fa-file-text` :guilabel:`Documents` smart button on their " +"profile." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3111 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3181 +msgid "Submitting the XML declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3113 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3183 +msgid "" +"After generating the XML file, it must be submitted to the Belgian tax " +"authorities. Ensure you are familiar with the `official submission process " +"`_." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3117 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the .bow format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3120 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3190 +msgid "" +"This conversion requires the use of a validation module available under the " +"*Technical Documentation* section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3123 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3193 +msgid "The validation module has two prerequisites:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3125 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3195 +msgid "Java 8 must be installed." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3126 +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3196 +msgid "" +"The certificate authority that signed the validation module must be " +"recognized." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3131 +msgid "281.45 Declaration" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3136 +msgid "" +"The Belgian fiscal declaration 281.45 is an annual statement that entities " +"must submit to the tax authorities, detailing the amounts of author's rights" +" and neighboring rights paid to beneficiaries. This declaration ensures " +"accurate tax reporting and compliance with Belgian tax regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3143 +msgid "" +"Odoo provides a streamlined process for generating the 281.45 declaration, " +"offering both a comprehensive XML file for electronic submission and " +"individual PDF files for record-keeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3149 +msgid "" +"To generate the global XML file in Odoo, navigate to :menuselection:`Payroll" +" app --> Reporting --> 281.45 Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/belgium.rst:3187 +msgid "" +"The XML files containing the fiscal data to be sent via the Belcotax-on-web " +"(BOW) application must be converted to the :file:`.bow` format." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:3 +msgid "Egypt" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:5 +msgid "" +"The Egypt **Payroll** localization package enables payroll processing that " +"fully complies with Egyptian labor laws. It calculates progressive income " +"tax, employee- and employer-paid social security, and core salary " +"components, including housing and transportation allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:12 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Egypt **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:18 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:20 +msgid "Name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:19 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:21 +msgid "Technical name" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:20 +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:21 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:22 +msgid "Description" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:21 +msgid ":guilabel:`Egypt - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:22 +msgid "`l10n_eg_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:23 +msgid "" +"Payroll module includes all salary rules, leave logic, and compensation " +"rules compliant with Egyptian Labor Law." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:25 +msgid ":guilabel:`Egypt - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:26 +msgid "`l10n_eg_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:27 +msgid "Adds account mappings related to payroll calculations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:30 +msgid "" +":doc:`Egypt fiscal localization documentation " +"<../../../finance/fiscal_localizations/egypt>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:33 +msgid "Egyptian employee contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:35 +msgid "" +"Once an employee has been :doc:`created in the database " +"<../../employees/new_employee>`, a :ref:`contract must be created " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:38 +msgid "" +"To check if the user already has a contract, navigate to the **Employees** " +"app, then click on the employee's Kanban card. The :icon:`fa-book` " +":guilabel:`Contracts` smart button displays a red zero when no contract " +"exists. Otherwise, it displays :guilabel:`In contract since (contract start " +"date)` in green." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:44 +msgid "" +"Contracts can also be found by navigating to :menuselection:`Employees app " +"--> Employees --> Contracts`. All contracts appear in a list view, grouped " +"by status." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:47 +msgid "" +"Populate the following contractual information in the :guilabel:`Salary " +"Information` tab of the contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:50 +msgid "" +":guilabel:`Social Insurance Reference Amount`: Used as the base amount for " +"calculating the :ref:`social insurance employee and employer portions " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:53 +msgid "" +":guilabel:`Number of Leave Days`: Used for calculating the :ref:`provision " +"amount for the annual leave for the employee " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:55 +msgid "" +":guilabel:`Provision Number of Days`: Corresponds with the number of days " +"used in the calculation of the :ref:`provision value of the end of service " +"for the employee `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:58 +msgid "" +":guilabel:`Total Number of Days`: Refers to the number of days used to " +"calculate the :ref:`end-of-service benefit paid to the employee when their " +"employment with the company ends `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:65 +msgid "Social insurance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:67 +msgid "" +"Social insurance rules calculate the contribution amounts that are to be " +"paid by the employer and employee to the :abbr:`NOSI (National Organization " +"for Social Insurance)`. This is only available for Egyptian employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:71 +msgid "" +"The employer contributes 18.75% of the social insurance reference amount for" +" the employee. On the other hand, the employee contributes 11% of their " +"insurance reference amount, and that amount gets deducted from the payslip " +"amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:76 +msgid "" +"The social insurance reference amount is set per employee in their " +"contracts." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:79 +msgid "Leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:81 +msgid "" +"The following leave types are available to employees working in Egypt: " +":ref:`Annual leave `, :ref:`Sick leave" +" `, :ref:`Unpaid leave " +"`, and :ref:`Other leave types " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:91 +msgid "" +"Employees are eligible for 21 days of annual leave, and if the employee " +"requires more days, they have to be :ref:`requested from HR managers " +"` accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:95 +msgid "" +"Since the annual leave is fully paid, it is not connected to a salary rule, " +"but it will appear on the worked days on the payslip form and on the PDF " +"printout." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:101 +msgid "Sick leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:103 +msgid "" +"Three cases exist for sick leaves in terms of the amount to be deducted from" +" the employee:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:105 +msgid "" +":guilabel:`Fully paid`: first 30 calendar days each year (affects only " +"working entries; no payroll deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:108 +msgid "**Payroll computation** =(Daily Wage)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:110 +msgid "" +":guilabel:`75% paid`: next 60 days; payroll rule deducts 25% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:112 +msgid "**Payroll computation** =(Daily Wage * 0.25)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:114 +msgid "" +":guilabel:`0% paid`: after 90 days; payroll rule deducts 100% of an " +"employee's salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:116 +msgid "**Payroll computation** =(Daily Wage * 0.00)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:121 +msgid "Unpaid leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:123 +msgid "" +"Deductions are applied on the employee's salary based on the number of " +"unpaid leave days taken, and it is calculated by dividing the monthly salary" +" for the employee by 30 to get the daily salary and then multiplying it by " +"the number of unpaid leave days taken." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:130 +msgid "Other leave types" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:132 +msgid "" +"These are leave types considered fully paid and do not affect the end " +"payslip, but are tracked in the working entries:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:135 +msgid "Maternity leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:136 +msgid "Hajj leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:137 +msgid "Death leave" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:140 +msgid "Income tax" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:142 +msgid "" +"In Egypt, employees are subject to a progressive income tax system, where " +"tax rates increase with higher annual income brackets." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:148 +msgid "" +"Depending on the annual income of the employee, the following rates apply:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:154 +msgid "Taxable Amount" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:155 +msgid "<600k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:156 +msgid "600k - 699k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:157 +msgid "700k - 799k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:158 +msgid "800k - 899k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:159 +msgid "900k - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:160 +msgid ">1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:161 +msgid "0%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:162 +msgid "1-40k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:168 +msgid "10%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:169 +msgid "More than 40k to 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:170 +msgid "1 - 55k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:175 +msgid "15%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:176 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:177 +msgid "More than 55k to 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:178 +msgid "1 - 70k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:182 +msgid "20%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:183 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:184 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:185 +msgid "More than 70k to 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:186 +msgid "1 - 200k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:189 +msgid "22.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:190 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:191 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:192 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:193 +msgid "More than 200k to 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:194 +msgid "1 - 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:196 +msgid "25%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:197 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:198 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:199 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:200 +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:201 +msgid "More than 400k" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:202 +msgid "1 - 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:203 +msgid "27.5%" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:209 +msgid "More than 1.2M" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:212 +msgid "Exemptions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:214 +msgid "" +"Employees are eligible to an EGP 20,000 personal exception on their gross " +"income." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:217 +msgid "Overtime" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:219 +msgid "" +"Depending on the time of day and the time at which the overtime is recorded " +"in, the additional amount to be paid to the employee can be as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:222 +msgid "" +"During daytime hours on working days, the amount is 1.35x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:223 +msgid "" +"During nighttime hours on working days, the amount is 1.70x times the " +"employee's hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:224 +msgid "" +"On rest days and public holidays: The amount is 2.0x times the employee's " +"hourly wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:227 +msgid "Overtime hours are registered as other inputs directly on payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:232 +msgid "Provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:234 +msgid "" +"Provisions are the amounts computed by the employer to account for the " +"payments made to the employee for :abbr:`EOS (end-of-service)` benefits or " +"annual leave. And it is computed on a monthly basis." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:238 +msgid "End of service benefit provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:240 +msgid "" +"It is computed by dividing the end of service Provision Number of Days by 12" +" and multiplying the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:243 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Provision Number of Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:249 +msgid "Annual leave provision" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:251 +msgid "" +"It is computed by dividing the number of leave days by 12 and multiplying " +"the result by the daily salary for the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:254 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Number of Leave Days}}{12} " +"\\times \\frac{\\text{Wage} + \\text{Allowances}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:262 +msgid "End of service" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:264 +msgid "" +"At the end of the service slip that is generated for the employee, there are" +" the following points that are unique only to the payslip:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:268 +msgid "Unused leaves compensation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:270 +msgid "" +"The number of available annual leaves is shown on the employee's record. It " +"is based on the annual leave type defined in the Payroll settings. It is " +"calculated as the total remaining allocations for that specific leave type " +"assigned to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:274 +msgid "" +"That number is then multiplied by the daily rate for the employee and added " +"as an allowance on their payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:278 +msgid "End of service benefit" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:280 +msgid "" +"It is calculated by multiplying the daily wage of the employee by the number" +" of days for the end of service that is set in the employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:283 +msgid "" +"\\text{Payroll computation} = \\frac{\\text{Wage + Allowances}}{30} \\times " +"\\text{End of Service Number of Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:289 +msgid "Out of contract" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:291 +msgid "" +"Out-of-contract days are the days that fall within the payslip period but " +"are not included in the employee's contract period. The corresponding amount" +" is added as a deduction on the payslip and is calculated by multiplying the" +" number of out-of-contract days by the employee's daily wage." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/egypt.rst:295 +msgid "" +"\\text{Payroll computation} = \\frac{\\text Wage + Allowances}{\\text{Days " +"in the Month}} \\times \\text{Out of Contract Days}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:3 +msgid "Employment Hero Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:5 +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, but the **journal entries** are done in " +"Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:11 +msgid "KeyPay was rebranded as **Employment Hero** in March 2023." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:18 +msgid "" +":ref:`Activate ` the :guilabel:`Employment Hero Payroll` " +"module (`l10n_employment_hero`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:20 +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/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "" +"Enabling Employment Hero Integration in Odoo Accounting displays new fields in the\n" +"settings" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:28 +msgid "" +"The API Key can be found in the :guilabel:`My Account` section of the " +"Employment Hero platform." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "\"Account Details\" section on the Employment Hero dashboard" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:33 +msgid "" +"The **Payroll URL** is left empty by default to avoid any confusion. Please " +"fill it according to the documentation specific to the localization." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:37 +msgid "" +"Employment hero is available for :ref:`Australia " +"`, :ref:`Malaysia `, :ref:`New Zealand `, :ref:`Singapore " +"`, and the :ref:`United Kingdom " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:43 +msgid "" +"The **Business ID** can be found in the Employment Hero URL. (i.e., " +"`189241`)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:0 +msgid "The Employment Hero Business ID number is in the URL" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:48 +msgid "Choose any Odoo journal to post the payslip entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:49 +msgid "" +"Configure the tax by going to :menuselection:`Accounting --> Configuration " +"--> Taxes`. Create the necessary taxes for the Employment Hero payslip " +"entries. Fill in the tax code from **Employment Hero** in the " +":guilabel:`Matching Employment Hero Tax` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:54 +msgid "How does the API work?" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "" +"Example of a Employment Hero Journal Entry in Odoo Accounting (Australia)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:63 +msgid "" +"By default, the synchronisation happens once per week. The records can be " +"fetched 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/hr/payroll/payroll_localizations/employment_hero.rst:67 +msgid "" +"Employment Hero payslip entries also work based on double-entry bookkeeping." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:69 +msgid "" +"The accounts used by Employment Hero are defined in the section " +":guilabel:`Payroll settings`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:-1 +msgid "Chart of Accounts menu in Employment Hero" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/employment_hero.rst:74 +msgid "" +"For the API to work, create the same accounts as the default accounts of the" +" Employment Hero business (**same name and same code**) in Odoo. The correct" +" account types must be chosen in Odoo to generate accurate financial " +"reports." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:3 +msgid "Hong Kong" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:8 +msgid "" +"Ensure the :guilabel:`Hong Kong - Payroll` (`l10n_hk_hr_payroll`) module is " +"installed before proceeding." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:14 +msgid "Create employees" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:16 +msgid "" +"Go to the :menuselection:`Employees` app and click :guilabel:`New`. Then, " +"configure the following fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:19 +msgid "Under the :guilabel:`Work Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:21 +msgid "" +":guilabel:`Working Hours`: :guilabel:`HK Standard 40 hours/week` option " +"**must** be selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:23 +msgid "Under the :guilabel:`Private Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:25 +msgid "" +":guilabel:`Surname, Given Name, Name in Chinese`: name of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:26 +msgid ":guilabel:`Private Address`: address of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:27 +msgid ":guilabel:`Bank Account Number`: employee's bank account number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:28 +msgid "" +":guilabel:`Current Rental`: employee's rental records (if rental allowance " +"is applicable)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:29 +msgid "" +":guilabel:`Autopay Type`: :guilabel:`BBAN`, :guilabel:`SVID`, " +":guilabel:`EMAL`, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:30 +msgid ":guilabel:`Autopay Reference`: autopay reference number." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:31 +msgid ":guilabel:`Identification No`: HKID of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:32 +msgid ":guilabel:`Gender`: gender of the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:35 +msgid "" +"For the :guilabel:`Bank Account Number`, this account should be set as " +":guilabel:`Trusted` before further processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:38 +msgid "" +"To achieve this, click on the right-arrow button next to :guilabel:`Bank " +"Account Number` field. Set the :guilabel:`Send Money` to :guilabel:`Trusted`" +" by clicking on the toggle." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:42 +msgid "" +"To populate the :guilabel:`Current Rental`, click on the :guilabel:`History`" +" button. Then, click on :guilabel:`New`. Fill in the relevant details and " +"save the rental record. Upon saving the record, the rental contract " +":guilabel:`state` will be visible (at the top-right corner) and can be set " +"to :guilabel:`Running`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:47 +msgid "Under the :guilabel:`HR Settings` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:49 +msgid "" +":guilabel:`Volunteer Contribution Option`: select either :guilabel:`Only " +"Mandatory Contribution`, :guilabel:`With Fixed %VC`, or :guilabel:`Cap 5% " +"VC`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:51 +msgid ":guilabel:`MPF Manulife Account`: account number, if applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:56 +msgid "Manage contracts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:58 +msgid "" +"Once the new employee has been created, click the :guilabel:`Contracts` " +"smart button on the employee record, or navigate to " +":menuselection:`Employees app --> Employees --> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:62 +msgid "" +"Only **one** contract can be active simultaneously per employee, but an " +"employee can be assigned consecutive contracts during their employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:65 +msgid "The following are critical for setting up a contract:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:67 +msgid "" +":guilabel:`Salary Structure Type`: set as :guilabel:`CAP57: Hong Kong " +"Employee`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:68 +msgid ":guilabel:`Contract Start Date`: start date of employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:69 +msgid "" +":guilabel:`Working Schedule`: set as :guilabel:`HK Standard 40 hours/week` " +"(from employee record)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:70 +msgid "" +":guilabel:`Work Entry Source`: select either :guilabel:`Working Schedule`, " +":guilabel:`Attendances` or :guilabel:`Planning`. This field determines how " +"the work entries are accounted for in the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:74 +msgid "" +":guilabel:`Working Schedule`: the work entries are generated automatically " +"based on the employee's working schedule." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:76 +msgid "" +":guilabel:`Attendances`: the work entries are generated based on the check-" +"in/out period logged in the *Attendances*." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:78 +msgid "" +":guilabel:`Planning`: the work entries are generated from planning shifts " +"only." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:80 +msgid "Under the :guilabel:`Salary Information` tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:82 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:61 +msgid "" +":guilabel:`Wage Type`: select :guilabel:`Fixed Wage` for Full-time or Part-" +"time employees, or :guilabel:`Hourly Wage` for employees who are paid " +"hourly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:84 +msgid ":guilabel:`Schedule Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:85 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:64 +msgid "" +":guilabel:`Wage`: :guilabel:`Monthly` or :guilabel:`Hourly` depending on the" +" :guilabel:`Wage Type`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:87 +msgid "" +":guilabel:`Internet Subscription`: this is an **optional** field to provide " +"additional internet allowance on top of the current salary package." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:91 +msgid "Timesheets do **not** impact work entries in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:93 +msgid "" +"Once all information has been setup, set the contract status to " +":guilabel:`Running` by clicking the :guilabel:`Running` button in the top-" +"right of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong employment contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:102 +msgid "Generate payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:104 +msgid "" +"Once the employees, and their contracts, are configured, payslips can be " +"generated in the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:107 +msgid "" +"Odoo provides **four** different salary structures under CAP57 regulation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:109 +msgid "" +":guilabel:`CAP57: Employees Monthly Pay`: to process the monthly employee " +"salary." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:110 +msgid "" +":guilabel:`CAP57: Payment in Lieu of Notice`: to process final payment upon " +"contract termination using :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:112 +msgid "" +":guilabel:`CAP57: Long Service Payment`: applicable to employees with more " +"than five years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:114 +msgid "" +":guilabel:`CAP57: Severance Payment`: applicable to employees with more than" +" two years of service upon contract termination." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:117 +msgid "" +"Before running the payslips, the accounts used in the salary rule can be " +"adjusted by navigating to :menuselection:`Payroll app --> Configuration --> " +"Rules`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary Rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:123 +msgid "" +"Odoo can create pay runs in two ways: via :ref:`batch " +"` or :ref:`individual " +"` payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:129 +msgid "Batch payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:131 +msgid "" +"This method of payslip generation is used for recurring payments, since " +"multiple employee payslips can be managed at once. Go to " +":menuselection:`Payroll app --> Payslips --> Batches`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:134 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:158 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:399 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:418 +msgid "Click on :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:135 +msgid "" +"Enter a :guilabel:`Batch Name` (e.g. `2024 - Jan`) and :guilabel:`Period` " +"(e.g. `01/01/2024` - `01/31/2024`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:137 +msgid "Click on :guilabel:`Generate Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:138 +msgid "" +"Choose which :guilabel:`Salary Structure` to use for this batch. The " +"department filter allows the batch to only apply to a specific group of " +"employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:140 +msgid "Click on :guilabel:`Generate`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:141 +msgid "A :guilabel:`Payslips` smart button is created automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:143 +msgid "" +"Next, click :guilabel:`Create Draft Entry` to generate a draft journal entry" +" found in the :guilabel:`Other Info` tab of each payslip. A " +":guilabel:`Confirmation` pop-up window appears asking :guilabel:`Are you " +"sure you want to proceed?`. Click :guilabel:`Ok` to create the journal " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:150 +msgid "Individual payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:152 +msgid "Go to :menuselection:`Payroll app --> Payslips --> All Payslips`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:154 +msgid "" +"This method of payslip generation is commonly used to handle non-recurring " +"payments (e.g. :guilabel:`CAP57: Payment in Lieu of Notice`, " +":guilabel:`CAP57: Long Service Payment` or :guilabel:`CAP57: Severance " +"Payment`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:159 +msgid "" +"Select an :guilabel:`Employee`. When selected, the :guilabel:`Contract` is " +"filled out automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:161 +msgid "Add a pay :guilabel:`Period`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:162 +msgid "" +"Select a salary :guilabel:`Structure` (e.g. :guilabel:`CAP57: Employees " +"Monthly Pay`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:163 +msgid "" +"The :guilabel:`Worked Days & Inputs` tab automatically compute the worked " +"days/hours and time off leaves that are applicable." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:165 +msgid "" +"Additional payslip items can be added at this time (e.g. " +":guilabel:`Commissions`, :guilabel:`Deductions`) under the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:167 +msgid "" +"Click on :guilabel:`Compute Sheet` button to generate the payslip lines. " +"This button updates the :guilabel:`Salary Computation` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:171 +msgid "" +"If the work entry for an employee was amended, click the :icon:`fa-cog` " +":guilabel:`(gear)` icon, then click :guilabel:`Recompute Whole Sheet` to " +"refresh the payslip's :guilabel:`Worked Days & Inputs` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:175 +msgid "" +"The :guilabel:`Salary Computation` tab shows the detailed breakdown of the " +"computation, based on the salary rules configured for each structure type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:178 +msgid "" +":guilabel:`Rent Allowance`: amount derived from the employee's active rental" +" record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:179 +msgid "" +":guilabel:`Basic Salary`: amount of base salary provided (after rent " +"allowance deduction)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:180 +msgid "" +":guilabel:`713 Gross`: net payable amount considering *Commission*, " +"*Internet Allowance*, *Reimbursements*, *Back-pay*, *Deduction*, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:182 +msgid "" +":guilabel:`MPF Gross`: net payable amount from 713 gross after consideration" +" of additional allowances, deductions, and end-of-year payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:184 +msgid "" +":guilabel:`Employee Mandatory Contribution`: employee MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:185 +msgid "" +":guilabel:`Employer Mandatory Contribution`: employer MPF Contribution." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:186 +msgid "" +":guilabel:`Gross`: net payable amount from MPF gross after consideration of " +"MPF deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:187 +msgid "" +":guilabel:`Net Salary`: final payable amount to be paid to the employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:190 +msgid "" +"There are no MPF contributions for the first month. Both employee and " +"employer contribution starts on second month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:196 +msgid "" +"Under the :guilabel:`Other Inputs` section in :guilabel:`Worked Days & " +"Inputs` tab, there are additional manual input types:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:199 +msgid "" +":guilabel:`Back Pay`: additional salary payout can be included under this " +"category." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:200 +msgid "" +":guilabel:`Commission`: the commission earned during the period can be " +"manually entered here." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:201 +msgid "" +":guilabel:`Global Deduction`: a lump-sum deduction from the entire payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:202 +msgid "" +":guilabel:`Global Reimbursement`: a lump-sum reimbursement to the entire " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:203 +msgid "" +":guilabel:`Referral Fee`: the additional bonus offered for any form of " +"business-related referral." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:204 +msgid "" +":guilabel:`Moving Daily Wage`: to override the :abbr:`ADW (Average Daily " +"Wage)` value used for leaves computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:206 +msgid "" +":guilabel:`Skip Rent Allowance`: if set, the rental allowance is excluded " +"from the current payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:208 +msgid "" +":guilabel:`Custom Average Monthly Salary`: to override the average monthly " +"salary used for end-of-year payment (rule is only applicable to payslips " +"generated in December)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:210 +msgid "" +":guilabel:`Lieu of Notice Period (Months)`: only applicable to " +":guilabel:`CAP57: Payment in Lieu of Notice` salary structure. By default, " +"the final payout is set as 1-month. Use the :guilabel:`Count` field under " +"the :guilabel:`Other Inputs` section to set a different notice period " +"duration." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:215 +msgid "" +"Once the payslips are ready, click on :guilabel:`Compute Sheet`, followed by" +" :guilabel:`Create Draft entry` to generate a draft journal entry found in " +"the :guilabel:`Other Info` tab of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:221 +msgid "" +"Once the draft journal entries have been posted, the company can now pay the" +" employees. The user can choose between **two** different *payment methods*:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:224 +msgid "" +"From the employee's payslip (:menuselection:`Payroll app --> Payslips --> " +"All Payslips`), once the payslip's journal entry has been posted, click " +":guilabel:`Register Payment`. The process is the same as :doc:`paying vendor" +" bills <../../../finance/accounting/payments>`. Select the desired bank " +"journal and payment method, then later reconcile the payment with the " +"corresponding bank statement." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:228 +msgid "" +"For batch payments (:menuselection:`Payroll app --> Payslips --> Batches`), " +"once all draft journal entries from the batch are confirmed, click " +":guilabel:`Mark as Paid` to post the payment journal entry. Then " +":doc:`create a payment <../../../finance/accounting/payments>` in the " +"*Accounting* app, and reconcile accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:234 +msgid "Attendances and hourly wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:236 +msgid "" +"To configure the contract for an employee paid hourly using the " +"*Attendances* app for hours tracking, navigate to :menuselection:`Payroll " +"app --> Contracts --> Contracts`. Create a new :ref:`contract " +"`. It is important to remember to set the " +":guilabel:`Work Entry Source` as :guilabel:`Attendances`, and " +":guilabel:`Wage Type` as :guilabel:`Hourly Wage`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:242 +msgid "To record the hours logged by the employee using *Attendances* app:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:244 +msgid "Go to :menuselection:`Attendances app`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:245 +msgid "" +"The employee can check-in/out, via the kiosk mode and the time will be " +"logged automatically." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:246 +msgid "" +"In the :menuselection:`Payroll app`, review the attendance work entries " +"generated from :menuselection:`Payroll app --> Work Entries --> Work " +"Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:248 +msgid "" +"Next, generate the :ref:`payslips ` and " +"process the payment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Work Entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Attendance Payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:257 +msgid "Time Off with Payroll" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:259 +msgid "" +"The work entry types and time off types are fully integrated between the " +"*Time Off* and *Payroll* apps. There are several default time off types and " +"work entry types specific to Hong Kong which are installed automatically " +"along with the *Hong Kong - Payroll* module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:263 +msgid "" +"Go to :menuselection:`Payroll app --> Configuration --> Work Entry Types` " +"and click :guilabel:`New`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:265 +msgid "" +"There are two checkboxes to be considered when setting up the work entry " +"type:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:267 +msgid "" +":guilabel:`Use 713`: Include this leave type as part of 713 computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:268 +msgid ":guilabel:`Non-full pay`: 80% of the :abbr:`ADW (Average Daily Wage)`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Work Entry Type." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:274 +msgid "" +":ref:`Creating and configuring work entry types `" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:277 +msgid "Understanding 713 Ordinance" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:279 +msgid "" +"The *Hong Kong - Payroll* module is compliant with 713 Ordinance which " +"relates to the :abbr:`ADW (Average Daily Wage)` computation to ensure fair " +"compensation for employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:282 +msgid "The ADW computation is as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "Hong Kong ADW Formula." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:287 +msgid "" +":abbr:`ADW (Average Daily Wage)` equals the total wage in a 12-month period," +" minus the wages of non-full pay, divided by the total days in a 12-month " +"period minus the days of non-full pay." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:291 +msgid "" +"For 418 compliance, there is no automated allocation of the *Statutory " +"Holiday* entitlement to the employees. As soon as 418 requirements are met, " +"manually allocate the leaves, via the *Time Off* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:296 +msgid "" +"Before generating payslips, ensure the statuses are :guilabel:`Done` to " +"validate the outcome." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:301 +msgid "Period" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:302 +msgid "Days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:303 +msgid "Wage" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:304 +msgid "Commission" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:305 +msgid "Total" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:306 +msgid "ADW" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:307 +msgid "Leave Value" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:308 +msgid "Jan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:309 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:323 +msgid "31" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:310 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:312 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:317 +msgid "$20200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:311 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:325 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:332 +msgid "$0" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:313 +msgid "$651.61 ($20200/31)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:314 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:321 +msgid "N/A" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:315 +msgid "Feb" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:316 +msgid "28" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:318 +msgid "$5000" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:319 +msgid "$25200" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:320 +msgid "$769.49 ($45400/59)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:322 +msgid "Mar (One Day Annual Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:324 +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:326 +msgid "$20324.33" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:327 +msgid "$730.27 ($65724.33/90)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:328 +msgid "$769.49" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:329 +msgid "Apr (One Day 80% Sick Leave)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:331 +msgid "$20117.56" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:335 +msgid "$584.22 ($730.27*0.8)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:338 +msgid "Here is an example demonstrating the 713 logic:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:340 +msgid "" +"**Jan**: Generate a payslip with a monthly wage of $20200. The :abbr:`ADW " +"(Average Daily Wage)` is always computed on a cumulative basis of the " +"trailing 12-months." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:342 +msgid "" +"**Feb**: Generate a similar payslip, but add an :guilabel:`Other Input Type`" +" for the :guilabel:`Commission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:344 +msgid "" +"**Mar**: Apply for **one** full-paid annual leave in March. The salary " +"compensation for the leave taken is based on :abbr:`ADW (Average Daily " +"Wage)` thus far." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong March 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:350 +msgid "" +"**Apr**: Apply for a 1-day non-full pay leave in April. Since this is a non-" +"full pay leave, the :abbr:`ADW (Average Daily Wage)` is computed " +"accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:0 +msgid "Hong Kong April 713." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:357 +msgid "" +"The value of :abbr:`ADW (Average Daily Wage)` is computed in the backend, " +"and not be visible to the user." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:361 +msgid "" +"`HK 713 Ordinance " +"`_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:362 +msgid "" +"`HK 418 Ordinance `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:365 +msgid "Generate reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:367 +msgid "" +"Before generating the below reports, setup the following in " +":menuselection:`Settings app --> Payroll`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:370 +msgid "Configure the following in the :guilabel:`Accounting` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:372 +msgid "Tick the :guilabel:`Payroll HSBC Autopay` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:374 +msgid ":guilabel:`Autopay Type`: Set as :guilabel:`H2H Submission`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:375 +msgid "Select the :guilabel:`Bank Account` to use." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:377 +msgid "Configure the following in the :guilabel:`HK Localization` section:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:379 +msgid ":guilabel:`Employer's Name shows on reports`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:380 +msgid ":guilabel:`Employer's File Number`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:381 +msgid ":guilabel:`Manulife MPF Scheme`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Payroll Settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:387 +msgid "IRD report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:389 +msgid "There are a total of **four** IRD reports available:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:391 +msgid ":guilabel:`IR56B`: employer's Return of Remuneration and Pensions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:392 +msgid ":guilabel:`IR56E`: notification of Commencement of Employment." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:393 +msgid "" +":guilabel:`IR56F`: notification of Ceasation of Employment (remaining in " +"HK)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:394 +msgid "" +":guilabel:`IR56G`: notification of Ceasation of Employment (departing from " +"HK permanently)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:396 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting`, and select one of the " +":guilabel:`IR56B/E/F/G Sheet` options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:400 +msgid "Fill in the relevant information for the IRD report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:401 +msgid "" +"Click on :guilabel:`Populate`, and the :guilabel:`Eligible Employees` smart " +"button appears." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:402 +msgid "" +"The :guilabel:`Employee Declarations` status is :guilabel:`Draft` and " +"changed to :guilabel:`Generated PDF` status once the schedule runs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:404 +msgid "Once the PDF is generated, the IRD form may be downloaded." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong IR56B report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:410 +msgid "" +"The scheduled action called *Payroll: Generate pdfs* can be manually " +"triggered. It is set by default to run the PDF generation monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:414 +msgid "Manulife MPF sheet" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:416 +msgid "" +"Go to :menuselection:`Payroll app --> Reporting --> Manulife MPF Sheet`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:419 +msgid "" +"Select the relevant :guilabel:`Year`, :guilabel:`Month`, and " +":guilabel:`Sequence No.`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:420 +msgid "Click on :guilabel:`Create XLSX`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:421 +msgid "" +"The *Manulife MPF XLSX* file is then generated, and available for download." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong Manulife Sheet." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:427 +msgid "" +"Odoo will not be developing further reports for other MPF trustee as there " +"will soon be an eMPF platform setup by the local government." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:431 +msgid "`eMPF `_" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:434 +msgid "HSBC autopay report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:436 +msgid "" +"If *HSBC Autopay* is selected as the batch payment method, click on " +":guilabel:`Create HSBC Autopay Report`, and fill in the mandatory fields:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:-1 +msgid "Hong Kong HSBC Autopay wizard." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/hong_kong.rst:442 +msgid "" +"This creates an :file:`.apc` file format which can be uploaded to the HSCB " +"portal for processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:3 +msgid "Jordan" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:5 +msgid "" +"The Jordan **Payroll** localization package offers a comprehensive solution " +"for managing payroll in compliance with Jordanian labor laws. It supports " +"income tax calculations using progressive tax brackets, social security " +"contributions from both employees and employers and basic salary " +"calculations, including allowances such as housing and transportation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:13 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the Jordan **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:22 +msgid ":guilabel:`Jordan - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:23 +msgid "`l10n_jo_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:24 +msgid "" +"Payroll module supporting basic calculation, tax income brackets, and " +"national contribution tax and social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:26 +msgid ":guilabel:`Jordan - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:27 +msgid "`l10n_jo_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:28 +msgid "Bridge module between **Payroll** and **Accounting**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:31 +msgid "" +":doc:`Jordan fiscal localization documentation " +"<../../../finance/fiscal_localizations/jordan>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:34 +msgid "Basic calculations" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:36 +msgid "" +"The Jordan **Payroll** localization package in Odoo provides foundational " +"payroll management tools that are compliant with Jordan's labor laws and " +"regulations. Key features include:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:39 +msgid "" +"**Basic salary calculations**: Odoo supports the computation of employee " +"salaries based on predefined salary structures, ensuring accurate payroll " +"processing." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:41 +msgid "" +"**Social security contributions**: It handles social security deductions for" +" employees and employer contributions, aligning with local regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:43 +msgid "" +"**Taxation support**: The system is configured to handle income tax " +"calculations in Jordan, including deductions based on progressive tax " +"brackets as required by Jordanian labor and tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:46 +msgid "" +"**Custom allowances and deductions**: The localization supports additional " +"allowances, deductions, or overtime as part of payroll computation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:49 +msgid "" +"These features ensure businesses can manage payroll effectively and comply " +"with Jordanian-specific legal requirements. For enhanced functionality, " +"businesses may leverage Odoo's flexibility to customize payroll workflows." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:54 +msgid "Social security" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:56 +msgid "" +"The Jordan **Payroll** localization package in Odoo simplifies social " +"security management by automating calculations for both employees and " +"employers. Contributions are based on a percentage of the employee's basic " +"salary, with a maximum insurable wage cap in line with Jordanian Social " +"Security Corporation (SSC) regulations." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:62 +msgid "Employee contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:64 +msgid "" +"Odoo calculates the employee's social security deduction as 7.5% of their " +"basic salary, up to the insurable wage cap of 3,000 JOD. If the employee's " +"salary exceeds this cap, the deduction is based on the capped amount. This " +"ensures compliance with :abbr:`SSC (Jordanian Social Security Corporation)` " +"requirements and reflects accurately on the employee's payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:70 +msgid "Employer contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:72 +msgid "" +"For employers, Odoo computes social security contributions as 14.25% of the " +"employee's basic salary, also capped at 3,000 JOD. Like the employee " +"contributions, if the salary exceeds this cap, the employer's contribution " +"is calculated based on the capped amount. These contributions include " +"pensions, workplace injury insurance, and other mandated benefits." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:80 +msgid "" +"**Capped contributions**: The system ensures that both employee and employer" +" contributions are aligned with the SSC-mandated insurance cap." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:82 +msgid "" +"**Automated calculations**: Contributions are automatically calculated and " +"included in payroll, reducing errors and administrative work." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:84 +msgid "" +"**Compliance with regulations**: Odoo's configuration ensures full " +"compliance with Jordanian social security laws, reflecting the correct rates" +" and caps for both sides." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:88 +msgid "Income tax calculation" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:90 +msgid "" +"The Jordan **Payroll** localization package automates income tax " +"calculations using progressive tax brackets, ensuring compliance with " +"Jordanian labor laws. The system applies income tax rates based on the " +"employee's annual gross income, with higher brackets subject to increased " +"percentages. The calculations are divided into six brackets, and the " +"appropriate tax is deducted monthly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:98 +msgid "" +"**5% bracket**: Applicable to annual gross income up to 5,000 JOD. Odoo " +"calculates 5% of the income within this range. If the gross income is below " +"5,000 JOD, the entire amount is taxed at 5%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:101 +msgid "" +"**10% bracket**: Applicable to annual gross income between 5,001 and 10,000 " +"JOD. Only the portion of income exceeding 5,000 JOD is taxed at 10%. For " +"example, if the gross income is 7,000 JOD, only 2,000 JOD is taxed at 10%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:104 +msgid "" +"**15% bracket**: Applicable to annual gross income between 10,001 and 15,000" +" JOD. The portion of income exceeding 10,000 JOD up to 15,000 JOD is taxed " +"at 15%. For instance, if the gross income is 12,000 JOD, only 2,000 JOD is " +"taxed at 15%." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:107 +msgid "" +"**20% bracket**: Applicable to annual gross income between 15,001 and 20,000" +" JOD. Income within this range is taxed at 20%, with deductions " +"automatically adjusted by Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:109 +msgid "" +"**25% bracket**: Applicable to annual gross income between 20,001 and " +"1,000,000 JOD. Income beyond 20,000 JOD up to 1,000,000 JOD is taxed at 25%." +" For higher incomes, Odoo ensures accurate calculations by applying the cap " +"of this range." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:112 +msgid "" +"**30% bracket**: Applicable to annual gross income exceeding 1,000,000 JOD. " +"Any income above this amount is taxed at 30%, with the system ensuring " +"accurate monthly deductions for high-income earners." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:117 +msgid "Automated process" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:119 +msgid "" +"Odoo determines the appropriate tax bracket for each employee based on their" +" gross annual income and applies the corresponding rates. These deductions " +"are prorated and deducted monthly, simplifying payroll management and " +"ensuring compliance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:126 +msgid "" +"**Progressive tax system**: Calculates taxes for each income range " +"individually, ensuring fairness and accuracy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:128 +msgid "" +"**Automated deductions**: Ensures a smooth payroll workflows with accurate " +"and timely monthly tax deductions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/jordan.rst:130 +msgid "" +"**Alignment with Jordanian regulations**: Fully complies with Jordanian tax " +"laws, minimizing manual intervention and errors." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:3 +msgid "United Arab Emirates" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:14 +msgid "" +":ref:`Install ` the following modules to get all the " +"features of the **United Arab Emirates** **Payroll** localization:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:23 +msgid ":guilabel:`United Arab Emirates - Payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:24 +msgid "`l10n_ae_hr_payroll`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:25 +msgid "Includes all rules, calculations, and salary structures." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:26 +msgid ":guilabel:`United Arab Emirates - Payroll with Accounting`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:27 +msgid "`l10n_ae_hr_payroll_account`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:28 +msgid "Includes all accounts related to the payroll module." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:31 +msgid "" +":doc:`United Arab Emirates fiscal localization documentation " +"<../../../finance/fiscal_localizations/united_arab_emirates>`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:37 +msgid "" +"First, configure the :doc:`employee general information " +"<../../employees/new_employee>` and then configure the following fields " +"under the :guilabel:`Private Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:40 +msgid "" +":guilabel:`Nationality (Country)`: The nationality affects an employee's " +"payslips, whether they are nationals or expats." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:42 +msgid "" +":guilabel:`Identification Number`: Used to extract the :ref:`WPS report " +"`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:44 +msgid "" +":guilabel:`Bank Account`: Used to extract the :ref:`WPS report " +"` and generate payments for those employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:48 +msgid "" +"The :guilabel:`Nationality (Country)` field needs to be set even if the " +"employee is a |UAE| national since there is a different type of handling if " +"they are citizens of a |GCC| country." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:54 +msgid "" +"Once the employee form has been created, ensure the :doc:`contract " +"<../contracts>` is enabled by clicking on the :icon:`fa-book` " +":guilabel:`Contracts` smart button, or going to :menuselection:`Employees " +"--> Contracts`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:58 +msgid "" +"The following contractual information related to employees working in the " +"United Arab Emirates are found under the :guilabel:`Salary Information` tab:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:63 +msgid ":guilabel:`Scheduled Pay`: the frequency of payslip issuance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:66 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid ":guilabel:`Housing Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:67 +msgid ":guilabel:`Transportation Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:68 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid ":guilabel:`Other Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:71 +msgid "" +"The allowance values set on the contract are used on the payslip lines as " +"allowances." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:73 +msgid "" +":guilabel:`Number of Leave Days`: Used to specify the number of annual leave" +" days that an employee deserves in a particular year. Regardless of the " +"actual number of leaves that the employee gets (extra leave days for some " +"internal company reasons), the final calculation of the end of service and " +"unpaid leaves is dependent on the number set on this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:79 +msgid "" +"The :guilabel:`Number of Leave Days` affects the calculation for unpaid " +"leave provisions." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:81 +msgid "" +":guilabel:`Is DEWS Applied`: DIFC Employee Workplace Savings (DEWS), if the " +"employee is a |UAE| national and has |DEWS| applied, tick this checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:83 +msgid "" +":guilabel:`Computed Based On Daily Salary`: Defines the way that the end of " +"service is calculated:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:85 +msgid "" +"Do not tick this checkbox if the standard calculation is to be used. This " +"computes the compensation amount by dividing the monthly salary by **30** " +"and then multiplying it by **21**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:87 +msgid "" +"Tick this checkbox and directly set the actual :guilabel:`Daily Salary` so " +"that it is used in the end of service calculation." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:91 +msgid "Salary structures and salary rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:94 +msgid "Other input rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:96 +msgid "" +"The following are the different allowances that can be defined directly on " +"the :doc:`payslip form <../payslips>` to allow for the values that are set " +"against these inputs to affect the |WPS| calculations as monthly variable " +"salaries for the specific employee that they are linked to." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:100 +msgid "" +"Rules that are related to the |WPS| setup, are linked to other input types, " +"and whenever they are used, their values are reflected on the |WPS| as " +"monthly variable salary for that specific employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Type**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:104 +msgid "**Code**" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid ":guilabel:`Conveyance Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:106 +msgid "`CONVALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:108 +msgid "`HOUALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid ":guilabel:`Medical Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:110 +msgid "`MEDALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid ":guilabel:`Annual Passage Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:112 +msgid "`ANNUALPASSALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid ":guilabel:`Overtime Allowance`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:114 +msgid "`OVERTIMEALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:116 +msgid "`OTALLOW`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid ":guilabel:`Leave Encashment`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:118 +msgid "`LEAVEENCASH`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:122 +msgid "End of service (EOS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:124 +msgid "" +"End of service (EOS) provides the calculation for the allowance that the " +"employee gets at the end of their service. It is triggered when the " +"employee's departure reason is set by archiving the employee's record." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:128 +msgid "There are several different calculations depending on the scenario:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:130 +msgid "" +"*The Employee spent less than a year in the company*: The employee does not " +"get any |EOS| allowance since they are not eligible for it (they are " +"eligible once they complete their first year in the company)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:133 +msgid "" +"*The Employee spent more than a year and less than 5 years in the company*: " +"The employee is eligible for an equivalent of **21** days of salary for each" +" year they spent on the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:137 +msgid "" +"There are two ways for calculating the daily wage that gets paid for the " +"employee against the 21 days of the |EOS|: Either by the default way of " +"dividing the monthly basic wage by 30. Or, it can be manually input on the " +"contract of the employee under the *Daily Salary* field." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:141 +msgid "" +"*The Employee spent more than 5 years in the company*: The employee is " +"eligible for an equivalent of **30** days of salary for each year they spent" +" on the company. In this case, if the default method is used, then the " +"employee gets paid an equivalent of 1 month of salary, and the set *Daily " +"Salary* field, they will get the amount for the day multiplied by 30." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:147 +msgid "" +"There are two payslips printout formats, one for normal salaries and one for" +" end of service payslips, it is based on the employee being archived and " +"having a departure reason or not." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:151 +msgid "End of service provision (EOS Provision)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:153 +msgid "" +"The |EOS| provision provides the calculation for the end-of-service " +"provision amount that the company puts aside every month to count for the " +"|EOS| that will be paid to them as an |EOS| allowance." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:157 +msgid "" +"Unlike the |EOS|, the provision is part of the employee's payslip from the " +"start of their contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:159 +msgid "" +"Just like the |EOS|, the provision has two calculations depending on the " +"period spent by the employee in the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:162 +msgid "" +"Less than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{21}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:163 +msgid "" +"More than 5 years: :math:`\\frac{\\text{Monthly " +"Wage}}{30}\\times{\\frac{30}{12}}`" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:166 +msgid "" +"This rule is not shown to the employee on the payslip printout and it does " +"not affect their net payable, it is only for internal use by the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:170 +msgid "Annual leave provisions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:172 +msgid "" +"Annual leave provisions are used for calculating the annual leave provision " +"accumulated each month, just like the |EOS| provision, it does not affect " +"the total amount paid to the employee, it is for internal use by the " +"company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:176 +msgid "" +"It is calculated by dividing the employee's total salary (Total Salary = " +"Wage + Allowances) by **30** to get the daily salary. The daily salary is " +"then multiplied by the eligible leave days and divided by **12** to " +"determine the monthly provision amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:180 +msgid "" +"\\text{Monthly Leave Provision} = \\frac{\\text{Total Salary} \\times \\text{Number of Leave Days}}{30}\n" +"\\div 12" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:187 +msgid "Social insurance contributions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:189 +msgid "" +"Social insurance contributions calculate the *social insurance*, which is " +"only available to |UAE| nationals." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:192 +msgid "" +"The company contributes **15%** of the total monthly salary for the employee" +" if the company is in **Abu Dhabi** and **12.5%** if the company is in " +"**another Emirate**." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:196 +msgid "" +"The total monthly salary for the employee = [basic + all allowances set on " +"the contract]." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:198 +msgid "" +"On the other hand, the employee contributes **5%** of their total monthly " +"salary and that amount gets deducted from the payslip amount." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:202 +msgid "Annual remaining leave balance rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:204 +msgid "" +"Annual remaining leave balance rules are used for calculating the amount to " +"be paid to or taken from the employee based on the number of leave days " +"deserved by the employee during the current year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:207 +msgid "" +"The annual leave :ref:`time off type ` is specified" +" using the :guilabel:`Is Annual Leave` checkbox." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:210 +msgid "" +"If enabled, the rule calculates the amount of leave days deserved by the " +"employee up to the current date and subtracts the number of annual leave " +"days taken, and if the result is positive, this means that the employee " +"should be compensated for remaining amount and if negative this means that " +"the employee is liable to the company for the difference." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:216 +msgid "Sick leave rules" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:218 +msgid "" +"Sick leave rules provide the calculation for cases where the employee is on " +"sick leave and decides how the payslip should be affected." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:221 +msgid "There are **3 cases** for the employee to have:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:223 +msgid "" +"**Fully paid sick leave:** The employee can upload a sick leave certificate " +"(SLI). Employees are eligible for **15 days** of this type of leave per " +"calendar year." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:227 +msgid "" +"The SLI is not mandatory in Odoo but can be done from the setup of the " +":ref:`time off types `." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:230 +msgid "" +"**50% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **30 days** from this leave type. These 30 days are counted " +"after the first **15** fully paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:233 +msgid "" +"**0% paid sick leave:** Same as the fully paid one, but the employees are " +"eligible for **45 days** from this leave type. These **45 days** are counted" +" after the first **15/30** fully/half-paid days." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:238 +msgid "" +"As per the labor law of the United Arab Emirates, the 15, 30, 45 days are " +"not specified as working days or calendar days so this point will rely on " +"the company policy." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:241 +msgid "" +"The amount paid for the employee per sick leave day is counted as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:244 +msgid "" +"\\frac{\\text{Number of Leave Days} \\times \\text{Gross Per Month}}{30} " +"\\times \\text{Percentage}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:249 +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:274 +msgid "" +"Where the gross per month is the basic + all other allowances set on the " +"employee's contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:252 +msgid "Daman investments end of service programme (DEWS)" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:254 +msgid "" +"|DEWS| allows for calculating the |DEWS| amounts for the employees who are " +"eligible for it and would like to be registered on it under their current " +"contract with the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:257 +msgid "" +"It is calculated based on the number of years that employees have spent in " +"the company:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:259 +msgid "" +"**Less than 5 years:** 5.83% is deducted from the employee's **BASIC** " +"salary towards the DEWS." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:260 +msgid "" +"**More than 5 years:** 8.33% of The employee's **BASIC** is deducted from " +"the total payable for that employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:264 +msgid "Unpaid leaves" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:266 +msgid "" +"Unpaid leaves allows for calculating the amount to be deducted when an " +"employee takes an unpaid leave. It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:269 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{30}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:277 +msgid "Out of contract days" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:279 +msgid "" +"The out of contract days rule provides a calculation for the days " +"before/after the contract period that overlaps with the contract of days on " +"the employee's payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:283 +msgid "" +"Payslips are generated for the period of 1st-30th of September but the " +"contract expires on the 21st, in this case, there are 7 days flagged as out " +"of contract." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:286 +msgid "It is calculated by the following equation:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:288 +msgid "" +"\\frac{\\text{Total Number of Unpaid Leave Days} \\times \\text{Gross Per " +"Month}}{\\text{Number of Days in Current Month}}" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:294 +msgid "Manual deductions" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:296 +msgid "" +"Manual deductions allows the user to add manual deductions to be applied to " +"employees per payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:298 +msgid "" +"The amount to be deducted and the description of the deduction is to be set " +"directly on the payslip manually as other inputs." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:302 +msgid "Net salary" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:304 +msgid "" +"Net salary showcases the net amount that the employee will get based on the " +"payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:306 +msgid "" +"It is calculated by adding basic to all allowances and deducting all " +"deductions from it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:309 +msgid "" +"The approach taken for the rules above is to first get the full amounts for " +"all static amounts that are set on the contract and then deduct the amounts " +"that should be deducted such as unpaid leaves, sick leaves, manual " +"deductions, commission, etc." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:314 +msgid "Generating accounting entries from payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:316 +msgid "" +"The accounts are linked to each payroll rule as a debit or credit so that " +"when a draft entry is generated from a payslip, the amounts are reflected on" +" the accounts accordingly." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:319 +msgid "" +"The accounts need to be set in a way that would make the end-result entry " +"balanced, otherwise a warning is raised if it is not balanced and it will " +"not generate the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:322 +msgid "" +"After reviewing the payslips and making sure that all the amounts are " +"correct, generate a draft entry, either one entry for all employees or an " +"entry per employee depending on the setup done on the settings." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:327 +msgid "Debit and credit accounts set up for the basic and allowance rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:0 +msgid "Accounting setup for the rules." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:335 +msgid "" +"After a batch or a payslip's journal entry has been posted, the company can " +"proceed to pay their employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:338 +msgid "" +"In the batch itself or on the payslip, by clicking on the pay button, a " +"payment is created and linked to the posted entry for the payslip. The same " +"can be done for batch payslips if one payment is done from a single/multiple" +" payment bank/cash journal." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:343 +msgid "" +"Once the payslip is generated, the employee will be able to access the slips" +" from their portal users. They will automatically receive an email " +"mentioning that the payslips are now available to be viewed on their portal " +"view." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:348 +msgid "Payslip printouts" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:350 +msgid "" +"Two printout formats can be extracted from the payslip, it depends on the " +"type of the payslip either a *Monthly* payslip or an *End of Service* " +"Payslip. It is triggered if the employee for the payslip is generated is " +"archived during that month." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:355 +msgid "Master report" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:357 +msgid "" +"The *Master report* provides a detailed view of the amounts paid to " +"employees for a specific period based on the payslips that are generated for" +" them during that period with payslip lines being set as columns in an Excel" +" report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:361 +msgid "" +"It is mainly used to make the auditing process for the human resources " +"department easier and faster." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:363 +msgid "" +"To access this report, go to :menuselection:`Payroll --> Reporting --> " +"Master Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:368 +msgid "Wages protection system (WPS) reports" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:370 +msgid "" +"The |WPS| is a report that needs to be submitted by the company to prove " +"that they paid their employees the right amounts on the right dates. It can " +"either be generated per payslip or batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:373 +msgid "The following steps need to be followed before generating the report:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:375 +msgid "" +"Go to :menuselection:`Payroll --> Configuration --> Settings` and under the " +":guilabel:`UAE Payroll WPS Settings` section, configure the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:378 +msgid "" +":guilabel:`Employer Unique ID`: Set a unique identifier for the company to " +"be used in the |WPS| report." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:380 +msgid "" +":guilabel:`Salaries Bank Account`: Select a bank account or start typing to " +":guilabel:`Create and edit` a new bank account." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:384 +msgid "" +"When setting the :guilabel:`Salaries Bank Account` make sure to complete the" +" following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:386 +msgid ":guilabel:`Account Holder`: set as the company." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:387 +msgid ":guilabel:`Account Number`: has to be a valid IBAN." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:388 +msgid "" +":guilabel:`Bank`: has to have the :guilabel:`UAE Routing Code Agent ID` set." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:389 +msgid "" +":guilabel:`Send Money`: should be enabled and set to :guilabel:`Trusted`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:391 +msgid "" +"Set the unique identifier on all of the employees who are a part of the " +"target of the batch/payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:394 +msgid "" +"The :guilabel:`Identification No` field can be found on the employee's page " +"under the :guilabel:`Private Information` tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:397 +msgid "" +"Once the initial setup is done, the |WPS| can be generated either for one " +"payslip or for a batch as follows:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:400 +msgid "Generate the payslip one by one or as a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:401 +msgid "Post the draft entity related to the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:402 +msgid "" +"Create the payment report and set the :guilabel:`Export Format` to " +":guilabel:`UAE WPS`." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:405 +msgid "" +"The report comes in a :file:`.sif` format as per the governmental " +"requirements, so either use software that can open :file:`.sif` files or " +"convert it to another format (:file:`.xslx`) to be able to review it." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:409 +msgid "The resulting file consists of the following:" +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:411 +msgid "" +"**Employee Detail Record** (**EDR**): includes details of the employees on " +"the batch. There should be one :abbr:`EDR (Employee Detail Record)` record " +"per employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:413 +msgid "" +"**Employee Variable Pay** (**EVP**): includes the details of the variable " +"salary the employee got on that payslip. If the employee has any. The " +"variable amounts are calculated from when other inputs are used that are " +"linked to the salary rules (:menuselection:`Payroll --> Configuration --> " +"Rules`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payroll_localizations/united_arab_emirates.rst:417 +msgid "" +"**Salary Control Record** (**SCR**): There should only be one :abbr:`SCR " +"(Salary Control Record)` per |WPS| file as it indicates the employer details" +" and the totals for the payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:3 +msgid "Payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:5 +msgid "" +"*Payslips* are generated by payroll officers through the " +":menuselection:`Payroll` application." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:7 +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:10 +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:20 +msgid "To pay" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:22 +msgid "" +"Click on :menuselection:`Payroll app --> Payslips --> To Pay` to see the " +"payslips that need to be paid." +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:29 +msgid "" +"Each payslip lists the :guilabel:`Reference` number for the individual " +"payslip, the :guilabel:`Employee` name, the :guilabel:`Batch Name`, the " +":guilabel:`Company`, the :guilabel:`Basic Wage`, :guilabel:`Gross Wage`, " +":guilabel:`Net Wage`, and the :guilabel:`Status` of the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:33 +msgid "" +"Click on an individual payslip entry to view the details for that individual" +" payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:38 +msgid "Create a new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:40 +msgid "" +"A new payslip can be created from either the :ref:`Payslips To Pay " +"` page or the :ref:`Employee Payslips ` page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:43 +msgid "" +"Create a new payslip by clicking the :guilabel:`New` button in the top-left " +"corner." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:45 +msgid "" +"A blank payslip form is loaded, where the necessary payslip information can " +"be entered." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:48 +msgid "Payslip form" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:50 +msgid "" +"On the blank payslip form, several fields are required. Most of the required" +" fields auto-populate after an employee is selected." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:53 +msgid "Fill out the following information on the payslip form:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:55 +msgid "" +":guilabel:`Employee`: type in the name of an employee, or select the desired" +" employee from the drop-down list in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:59 +msgid "" +"It is recommended to **only** create payslips for employees that are already" +" in the database. If there is no current employee record (and therefore no " +"employee contract) it is recommended to create the new employee in the " +"*Employees* application **before** creating payslips for that employee. " +"Refer to the :doc:`new employee <../employees/new_employee>` documentation " +"for instructions on how to add an employee." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:65 +msgid "" +":guilabel:`Period`: the first day to the last day of the *current* month " +"auto-populates the :guilabel:`Period` fields by default. The dates can be " +"changed, if desired." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:68 +msgid "" +"To change the start date, click on the first date in the :guilabel:`Period` " +"field to reveal a pop-up calendar. On this calendar, use the :guilabel:`< " +"(less-than)` and :guilabel:`> (greater-than)` icons to select the desired " +"month. Then, click on the desired day to select that specific date." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:73 +msgid "" +"Repeat this process to modify the end date for the payslip. These fields are" +" **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:74 +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. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:77 +msgid "" +":guilabel:`Batch`: using the drop-down menu in this field, select the batch " +"of payslips this new payslip should be added to." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:79 +msgid "" +":guilabel:`Structure`: using the drop-down menu, select the salary structure" +" type. Only the corresponding structures associated with the selected " +"contract for the employee appear as options." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:82 +msgid "" +"If no employee and/or no contract is selected yet, all available " +":guilabel:`Structures` appear in the list. Once an employee and/or contract " +"is selected, any unavailable :guilabel:`Structures` set for that employee " +"and/or contract do not appear. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The top fields for a new payslip all filled out for a February payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:91 +msgid "" +"Typically, after making a selection in the :guilabel:`Employee` field, Odoo " +"auto-populates all other required fields (besides the :guilabel:`Period` " +"field), but **only** if that information is already on that employee's form " +"in the *Employees* app." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:96 +msgid "" +"If modifications to auto-populated fields are made, 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:102 +msgid "Worked days & inputs tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:104 +msgid "" +":guilabel:`Worked Days`: 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:108 +msgid "" +":guilabel:`Other Inputs`: additional inputs affecting the payslip can be " +"entered in this section, such as deductions, reimbursements, and expenses." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:111 +msgid "" +"Click :guilabel:`Add a line` to create an entry in the :guilabel:`Other " +"Inputs` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:113 +msgid "" +"Using the drop-down menu in the :guilabel:`Type` column, select a " +":guilabel:`Type` for the input. Next, enter a :guilabel:`Description`, if " +"desired. Lastly, enter the amount in the :guilabel:`Count` field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the worked days and inputs tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:122 +msgid "Salary computation tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:124 +msgid "" +":guilabel:`Salary Computation`: the :guilabel:`Salary Computation` tab is " +"automatically filled in after the :guilabel:`Compute Sheet` button is " +"clicked. Doing so displays the wages, deductions, taxes, etc. for the entry." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the salary computation tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:133 +msgid "Other info tab" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:135 +msgid "" +":guilabel:`Payslip Name`: type in a name for the payslip in this field. The " +"name should be short and descriptive, such as `(Employee Name) April 2023`. " +"This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:137 +msgid "" +":guilabel:`Company`: select the company the payslip applies to using the " +"drop-down menu in this field. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:139 +msgid "" +":guilabel:`Close Date`: enter the date that the payment is made to the " +"employee in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:141 +msgid "" +"Click in the field to reveal a calendar pop-up window. Using the " +":guilabel:`< > (less-than/greater-than)` icons, navigate to the desired " +"month and year." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:144 +msgid "Then, click on the desired date to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:145 +msgid "" +":guilabel:`Date Account`: enter the date on which the payslip should be " +"posted in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:146 +msgid "" +":guilabel:`Salary Journal`: this field auto-populates after selecting an " +"existing :guilabel:`Employee`. This field **cannot** be edited, as it is " +"linked to the *Accounting* application. This field is **required**." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:149 +msgid "" +":guilabel:`Accounting Entry`: if applicable, this field is automatically " +"populated once the payslip is confirmed. This field **cannot** be modified." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:151 +msgid "" +":guilabel:`Add an Internal Note...`: any note or reference message for the " +"new entry can be typed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "The fields filled out in the other info tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:159 +msgid "Process the new payslip" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:161 +msgid "" +"When all the necessary information on the payslip is entered, click the " +":guilabel:`Compute Sheet` button. Upon doing so, all the information on the " +"payslip is saved, and the :guilabel:`Salary Computation` tab auto-populates," +" based on the information on the employee's contract or attendance records." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:166 +msgid "" +"If any modifications need to be made, first click the :guilabel:`Cancel` " +"button, then click the :guilabel:`Set to Draft` button. Make any desired " +"changes, then click the :guilabel:`Compute Sheet` button once again, and the" +" changes are reflected in the :guilabel:`Worked Days` and :guilabel:`Salary " +"Computation` tabs." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:171 +msgid "" +"Once everything on the payslip form is correct, click the :guilabel:`Create " +"Draft Entry` button to create the payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:174 +msgid "" +"Then, a confirmation pop-up window appears, asking :guilabel:`Are you sure " +"you want to proceed?`. Click :guilabel:`OK` to confirm." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:178 +msgid "" +"The database may need to be refreshed for the payslip and email to appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:180 +msgid "" +"To print the payslip, click the :guilabel:`Print` button. To cancel the " +"payslip, click the :guilabel:`Cancel` button." +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:187 +msgid "" +"Next, the payment must be sent to the employee. To do this, click the " +":guilabel:`Register 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:193 +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 appears when the :guilabel:`Make " +"Payment` button is clicked. Banking information can be found in the " +":ref:`Private Information ` tab on the employee's " +"card in the *Employees* app. 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:203 +msgid "" +"Odoo automatically checks bank account information. If there is an error " +"with the employee's listed bank account, an error appears in a pop-up " +"window, stating, *The employee bank account is untrusted.* If this error " +"appears, update the employee's bank account information on their " +":ref:`Employee Form `." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:208 +msgid "" +"If a payment needs to be cancelled or refunded, click the corresponding " +":guilabel:`Cancel` or :guilabel:`Refund` button, located at the top-left of " +"the screen." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:212 +msgid "" +"Before processing payslips, it is best practice to check the *Warnings* " +"section of the *Payroll* app dashboard. Here, all possible issues concerning" +" payroll appear." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:215 +msgid "" +"To view the warnings, navigate to :menuselection:`Payroll app --> " +"Dashboard`. The warnings appear in the top-left corner of the dashboard." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The dashboard view of the Payroll app, with the warnings box highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:222 +msgid "" +"Warnings are grouped by type, such as `Employees Without Running Contracts` " +"or `Employees Without Bank account Number`. Click on a warning to view all " +"entries associated with that specific issue." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:225 +msgid "" +"If the warnings are not resolved, at any point in the payslip processing " +"process, an error may occur. Errors appear in a pop-up window, and provide " +"details for the error, and how to resolve them." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:232 +msgid "All payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:234 +msgid "" +"To view all payslips, regardless of status, go to :menuselection:`Payroll " +"app --> Payslips --> All Payslips`. The :guilabel:`Employee Payslips` page " +"loads, displaying all payslips, organized by batch, in a default nested list" +" view." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:238 +msgid "" +"Click on the :guilabel:`▶ (right arrow)` next to an individual batch name to" +" view all the payslips in that particular batch, along with all the payslip " +"details." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:241 +msgid "" +"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 one of the following status options:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:245 +msgid "" +":guilabel:`Draft`: 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:247 +msgid "" +":guilabel:`Waiting`: the payslip has been calculated, and the salary details" +" can be found in the *Salary Computation* tab." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:249 +msgid ":guilabel:`Done`: the payslip is calculated and ready to be paid." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:250 +msgid ":guilabel:`Paid`: the employee has been 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:256 +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:259 +msgid "" +"A new payslip can be created from the :guilabel:`Employee Payslips` page, by" +" clicking the :guilabel:`New` 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 new " +"payslips ` section." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:264 +msgid "" +"To print PDF versions of payslips from the *Payslips to Pay* or " +":guilabel:`Employee Payslips` pages, first select the desired payslips by " +"clicking on the individual checkbox to the left of each payslip to be " +"printed. Or, click the box to the left of the :guilabel:`Reference` column " +"title, 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:270 +msgid "" +"Payslips can also be exported to an Excel spreadsheet. To export **all** " +"payslips, click on the :guilabel:`⚙️ (gear)` icon at the end of the words " +":guilabel:`Employee Payslips` in the top-left corner. This reveals a drop-" +"down menu. Click :guilabel:`Export All` to export all payslips to a " +"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:279 +msgid "" +"To export only select payslips, first select the payslips to be exported " +"from the list. Then, click the checkbox to the left of each individual " +"payslip to select it. As payslips are selected, a smart button appears in " +"the top-center of the page, indicating the number of selected payslips. " +"Then, click the :guilabel:`⚙️ (gear) Actions` icon in the top-center of the " +"page, and click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "" +"The individual list of employee ayslips with three selected to be exported." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:290 +msgid "" +"Both *To Pay* and *All Payslips* display all the detailed information for " +"each payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:293 +msgid "Batches" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:295 +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:299 +msgid "" +"Each batch displays the :guilabel:`Name`, :guilabel:`Date From` and " +":guilabel:`Date To` dates, its :guilabel:`Status`, the number of payslips in" +" the batch (:guilabel:`Payslips Count`), 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:308 +msgid "Create a new batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:310 +msgid "" +"To create a new batch of payslips from the :guilabel:`Payslips Batches` page" +" (:menuselection:`Payroll app --> Payslips --> Batches`), click the " +":guilabel:`New` button in the top-left corner. Doing so reveals a blank " +"payslip batch form on a separate page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:314 +msgid "On the new payslip batch form, enter the :guilabel:`Batch Name`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:316 +msgid "" +"Next, select the date range to which the batch applies. Click into one of " +"the :guilabel:`Period` fields, and a calendar pop-up window appears. From " +"this calendar pop-up window, navigate to the correct month, and click on the" +" corresponding day for both the start and end dates of the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:320 +msgid "" +"The current company populates the :guilabel:`Company` field. If operating in" +" a multi-company environment, it is **not** possible to modify the " +":guilabel:`Company` from the form. The batch **must** be created while in " +"the database for the desired company." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:-1 +msgid "Enter the details for the new batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:331 +msgid "Process a batch" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:333 +msgid "" +"Click on an individual batch to view the details for that batch on a " +"separate page. On this batch detail page, different options (buttons) appear" +" at the top, depending on the status of the batch:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:336 +msgid "" +":guilabel:`New` status: batches without any payslips added to them have a " +"status of :guilabel:`New`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of new, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:343 +msgid "" +":guilabel:`Add Payslips`: click the :guilabel:`Add Payslips` button to add " +"payslips to the batch, and an :guilabel:`Add Payslips` pop-up window " +"appears. Only payslips that can be added to the batch (payslips not " +"currently part of a batch) appear on the list." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:347 +msgid "" +"Select the desired payslips by clicking the checkbox to the left of each " +"payslip name, then click the :guilabel:`Select` button to add them to the " +"batch. Once payslips are selected and added to the batch, the status changes" +" to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:351 +msgid "" +":guilabel:`Generate Payslips`: after payslips have been added to the batch, " +"click the :guilabel:`Generate Payslips` button to process the payslips and " +"create individual payslips in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:355 +msgid "" +"A :guilabel:`Generate Payslips` pop-up window appears. If only a specific " +":guilabel:`Salary Structure` and/or specific :guilabel:`Department` is " +"desired to make payslips for, select them from the corresponding drop-down " +"menus. If no selections are made, then all payslips listed in the pop-up " +"window are processed as usual." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:360 +msgid "" +"Click the :guilabel:`Generate` button to create the payslips. The " +":guilabel:`Generate Payslips` button changes to a :guilabel:`Create Draft " +"Entry` button, and the status changes to :guilabel:`Confirmed`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:364 +msgid "" +":guilabel:`Confirmed` status: batches that have been created and have " +"payslips in them, but the payslips have *not* been processed, have a status " +"of :guilabel:`Confirmed`. The following two button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "" +"A batch with a status of confirmed, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:372 +msgid "" +":guilabel:`Create Draft Entry`: click the :guilabel:`Create Draft Entry` " +"button to confirm the individual payslips (and the batch), and create a " +"draft of the payslips. The batch now has a status of :guilabel:`Done`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:375 +#: ../../content/applications/hr/payroll/payslips.rst:397 +msgid "" +":guilabel:`Set to Draft`: if at any point the batch needs to be reverted " +"back to a status of :guilabel:`New`, click the :guilabel:`Set to Draft` " +"button. This action does **not** remove any payslips that have already been " +"added to the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:379 +msgid "" +":guilabel:`Done` status: batches with confirmed payslips in them have a " +"status of :guilabel:`Done`. The following button options appear for these " +"batches:" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of done, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:386 +msgid "" +":guilabel:`Create Payment Report`: click the :guilabel:`Create Payment " +"Report` button, and a :guilabel:`Select a bank journal` pop-up window " +"appears. Select the correct bank journal from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:390 +msgid "" +"The batch name appears in the :guilabel:`File name` field, but this can be " +"modified, if desired. Finally, click :guilabel:`Confirm` to process the " +"payslips, and pay the employees." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:392 +msgid "" +":guilabel:`Mark as paid`: after the payments have been created via the " +":guilabel:`Create Payment Report` button, the payslips need to be marked as " +"paid in the database." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:395 +msgid "" +"Click the :guilabel:`Mark as paid` button, and the status of the batch " +"changes to :guilabel:`Paid`." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:401 +msgid "" +":guilabel:`Paid` status: batches that have been completed have a status of " +":guilabel:`Paid`. No other button options appear for this status." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:0 +msgid "A batch with a status of paid, with the available buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:408 +msgid "" +"On the batch detail page, the individual payslips in the batch are " +"accessible, via the :guilabel:`Payslips` smart button, located above the " +"batch information, in the center. Click the :guilabel:`Payslips` smart " +"button to view a list of all the individual payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:412 +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:416 +msgid "Generate warrant payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:418 +msgid "Commissions are paid to employees in Odoo using *warrant payslips*." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:420 +msgid "" +"Warrant payslips can be generated directly from the :guilabel:`Payslips " +"Batches` page (:menuselection:`Payroll app --> Payslips --> Batches`)." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:423 +msgid "" +"First, select the desired batches by clicking the box to the left of each " +"batch for which commission payslips should be created. Next, click the " +":guilabel:`Generate Warrant Payslips` button at the top of the page." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:427 +msgid "" +"Doing so reveals a :guilabel:`Generate Warrant Payslips` 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:434 +msgid "" +"In 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)` arrow icons, navigate to the correct month, and click on the date " +"to select it." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:439 +msgid "" +"In the :guilabel:`Department` field, select the desired department from the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:441 +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:444 +msgid "" +"Under the :guilabel:`Employee` section, enter the :guilabel:`Commission " +"Amount` for each employee in the far-right column. To remove an employee, " +"click the :guilabel:`🗑️ (trash)` icon to remove the line." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:448 +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:451 +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:454 +msgid "" +"Once all the commissions are properly entered, click the :guilabel:`Generate" +" Payslips` button to create the warrant payslips in a batch." +msgstr "" + +#: ../../content/applications/hr/payroll/payslips.rst:457 +msgid "" +":ref:`Process the batch ` in the same way as a " +"typical batch to complete the payment process." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:5 +msgid "" +"The *Reporting* section of the *Payroll* app offers a variety of reports to " +"choose from, organized by location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:8 +msgid "" +"The *Payroll* report, *Work Entry Analysis* report, and *Salary Attachment " +"Report* are default reports in the *Payroll* app, and are available for all " +"companies, regardless of location." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:11 +msgid "" +"Beneath the three default reports are all localization-based reports, " +"organized by country, in alphabetical order. These reports contain all the " +"various information for the offered benefits and local tax laws." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:15 +msgid "" +"To view all the available reports for the database, including all the " +"localization-specific ones, navigate to :menuselection:`Payroll app --> " +"Reporting` to view the available reports in a drop-down menu. Click on a " +"specific report to view it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Report dashboard view showing extra reports for Belgium databases." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:23 +msgid "" +"If a report is unavailable to a user, an :guilabel:`Invalid Operation` pop-" +"up window appears, stating: :guilabel:`You must be logged in to a (country) " +"company to use this feature`, where \"(country)\" is the specific country " +"the company is configured for." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:28 +msgid "Default reports" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:33 +msgid "" +"Click on :menuselection:`Payroll app --> Reporting --> Payroll` to display " +"the :guilabel:`Payroll Analysis` report. This report shows all the payslips " +"generated in the last 365 days, due to the default :ref:`filter " +"`: `Last 365 Days Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Payroll overview report showing payroll for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:41 +msgid "" +"The report can display metrics for a variety of parameters. Click the " +":guilabel:`Measures` box to view a drop-down menu with the various metric " +"options to display. The default options available include:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:45 +msgid ":guilabel:`# Payslip`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:46 +msgid ":guilabel:`Basic Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:47 +msgid ":guilabel:`Basic Wage for Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:48 +msgid ":guilabel:`Days of Paid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:49 +msgid ":guilabel:`Days of Unforeseen Absence`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:50 +msgid ":guilabel:`Days of Unpaid Time Off`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:51 +msgid ":guilabel:`Gross Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:52 +msgid ":guilabel:`Net Wage`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:53 +msgid ":guilabel:`Number of Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:54 +msgid ":guilabel:`Number of Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:55 +msgid ":guilabel:`Work Days`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:56 +msgid ":guilabel:`Work Hours`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:57 +msgid ":guilabel:`Count`" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:59 +msgid "" +":guilabel:`Net Wage` is the default metric for the :guilabel:`Payroll` " +"report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"The various measures available to display for the Payroll Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:66 +msgid "Line chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:68 +msgid "" +"A line chart is the default view for the *Payroll* report. If a different " +"view is selected, click the :guilabel:`Line Chart` button (represented by a " +":guilabel:`📈 (chart increasing)` icon) in the menu bar to change the view " +"back to a line chart." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:72 +msgid "" +"Several options are available for the line chart. Click the corresponding " +"button to activate the selection, and change the way the data is presented. " +"These icons appear at the end of the chart options. The various options are:" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:78 +msgid "" +":guilabel:`Stacked`: data is presented with each metric in its own line, " +"\"stacked\" on top of each other. This helps visualize the distribution and " +"variances between different categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:83 +msgid "" +":guilabel:`Cumulative`: data is presented with each metric on an individual " +"line, with the total amount calculated by combining all the lines. This " +"provides a comprehensive view of the cumulative data." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:89 +msgid "" +":guilabel:`Descending`: data is shown with the largest values on the left " +"side of the chart, gradually decreasing towards the smallest values on the " +"right side, along the x-axis. This arrangement helps emphasize trends or " +"outliers at the extremes." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:95 +msgid "" +":guilabel:`Ascending`: data is presented with the smallest values on the " +"left side of the chart, increasing towards the largest values on the right " +"side, along the x-axis. This arrangement can be useful for highlighting " +"progressive growth or trends." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:100 +msgid "These options can be combined to create a variety of views." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the line chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:107 +msgid "Bar chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:109 +msgid "" +"To display the data in a bar chart, click on the :guilabel:`Bar Chart` " +"button (represented by a :guilabel:`📊 (bar chart)` icon) in the menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:112 +msgid "" +"Click the :ref:`Stacked ` icon to view the bar chart in a " +"stacked format (where multiple values appear in each column). " +":ref:`Cumulative ` bar charts are useful for visualizing" +" the progression over time or other categories." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:116 +msgid "" +"An option to display the columns in :ref:`Descending ` " +"or :ref:`Ascending ` order appears at the end of the " +"options." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "" +"Menu buttons with the bar chart called out, along with the other option " +"buttons." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:124 +msgid "" +"Clicking an option enables it. To turn off the option, click it again. When " +"the option is enabled the icon appears lighter, with a turquoise outline. " +"When it is inactive, it appears gray, with no outline." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:129 +msgid "Pie chart" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:131 +msgid "" +"To display the data in a pie chart, click on the :guilabel:`Pie Chart` " +"button (represented by a :guilabel:`(pie chart)` icon) in the menu bar. " +"There are no additional options available in this view." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Menu buttons with the pie chart called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:140 +msgid "Pivot table" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:142 +msgid "" +"To display the data in a pivot table, click on the :guilabel:`Pivot` button " +"(represented by a :guilabel:`(pivot)` icon) located in the far-right side of" +" the top menu bar." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:145 +msgid "" +"The default information displayed includes the number of payslips " +"(:guilabel:`# Payslip`), the :guilabel:`Net Wage`, the :guilabel:`Gross " +"Wage`, the number of :guilabel:`Days of Paid Time Off`, and the number of " +":guilabel:`Days of Unpaid Time Off`. The information is organized by " +"department." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:149 +msgid "" +"To display more information on the report, click the :guilabel:`Measures` " +"button to reveal a drop-down menu. Then, click on any other metric to " +"display it on the pivot table." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Pivot table view with the various metrics called out." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:156 +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:160 +msgid "" +"To export the data in an XLSX format, click the :guilabel:`Download xlsx` " +"button, represented by a :guilabel:`⬇️ (down arrow above a horizontal bar)` " +"icon, located at the far-right of the available icons. The information is " +"then downloaded into a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The menu options with the download button highlighted." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:168 +msgid "" +"Any report can be inserted into a spreadsheet by clicking the " +":guilabel:`Insert in Spreadsheet` button. A :guilabel:`Select a spreadsheet " +"to insert your (type of report)` pop-up window appears, asking which " +"spreadsheet to place the information in. Select an existing spreadsheet or " +"dashboard, or select a new :guilabel:`Blank spreadsheet`. Click the " +":guilabel:`Confirm` button to move to a spreadsheet view with the report " +"added to it." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "The view of data sent to a spreadsheet." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:181 +msgid "" +"If the **Documents** app is **not** installed, the :guilabel:`Insert in " +"Spreadsheet` option places the newly-created spreadsheet in the " +"**Dashboards** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:184 +msgid "" +"If the **Documents** application *is* installed, the spreadsheet has the " +"option to be stored in either the **Dashboards** app or **Documents** app." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:190 +msgid "Filters" +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:192 +msgid "" +"At the top of each report, the default filters are shown inside the " +":guilabel:`Search...` box." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:194 +msgid "" +"Click the :guilabel:`⬇️ (down arrow)` icon in the search bar to display the " +"available :guilabel:`Filters`. Filters show information that match the " +"specific filter parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:198 +msgid "" +"The :guilabel:`Work Entries Analysis` report has two default filters, the " +"`Current month:(Month) (Year)` filter, and the `Validated` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:-1 +msgid "Filters enabled for the Work Entries Analysis report." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:205 +msgid "" +"The :guilabel:`Payroll` report has only one default filter, the `Last 365 " +"Days Payslip` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:207 +msgid "" +"The :guilabel:`Salary Attachment Report` has only one default filter, the " +"`Payslip End Date: (Year)` filter." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:210 +msgid "" +"All reports can include custom filters, or group information, by different " +"metrics (employee, department, company, etc.)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:213 +msgid "" +"Some reports have the option to compare the current report to the previous " +"time period or year (a :guilabel:`Comparison` option)." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:216 +msgid "" +"Click on a parameter to select it and activate it. The report is immediately" +" updated with the new parameters." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:219 +msgid "" +"The updated report can be set as a *favorite* report, meaning the parameters" +" are stored for quick access in the future. To do that, click " +":guilabel:`Save the current search`, under the :guilabel:`Favorites` " +"section, located in the search bar drop-down mega menu of filter options. " +"Doing so reveals two options and a :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:224 +msgid "" +"To set the current report as the default configuration when the report is " +"accessed, check the box next to :guilabel:`Default filter`. If the current " +"report should be accessible to everyone in the database, check the box next " +"to :guilabel:`Share`." +msgstr "" + +#: ../../content/applications/hr/payroll/reporting.rst:228 +msgid "" +"Finally, click :guilabel:`Save`, which saves the currently configured " +"report. Then, it appears beneath the :guilabel:`Favorites` in the search bar" +" drop-down mega menu of filter options." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:3 +msgid "Salary attachment report" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:5 +msgid "" +"*Salary attachments* in Odoo refer to a portion of an employee's earnings " +"that are designated for a specific purpose, both voluntary and involuntary. " +"These can include contributions to a retirement plan, repayment of a loan, " +"wage garnishments, or child support." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:9 +msgid "" +"Voluntary salary attachments, such as repaying a loan, or contributing to a " +"charity on a monthly basis, are considered *Assignments of Salary* in Odoo. " +"Salary attachments that are required, such as a lawsuit settlement " +"repayment, or repaying a tax lien, are considered *Attachments of Salary* in" +" Odoo. Child support payments have their own category, and are simply " +"referred to as *Child Support* in Odoo." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:15 +msgid "" +"To view this report, navigate to :menuselection:`Payroll app --> Reporting " +"--> Salary Attachment Report`. The :guilabel:`Salary Attachment Report` " +"shows all deductions or allocations per employee, organized by payslip, in a" +" default pivot table. The default filter is the end of the current year " +"(:guilabel:`Payslip End Date: (year)`). The employees populate the rows, " +"while the various deductions populate the columns, organized by type of " +"deduction, and further grouped by individual payslip." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:22 +msgid "" +"The default report contains **all** payslips for the current year, so the " +"report typically contains a large number of columns. This could make it " +"difficult to view all the data at once, as the report may be very wide and " +"require scrolling to view all the data." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:26 +msgid "" +"To view a condensed version of salary attachments, and have all the salary " +"attachment columns visible on one page, click the :icon:`fa-minus-square-o` " +":guilabel:`Total` icon at the top of the report, above the various payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:30 +msgid "" +"This presents the salary attachments for the current year, and only displays" +" three columns, :guilabel:`Attachment of Salary`, :guilabel:`Assignment of " +"Salary`, and :guilabel:`Child Support.`" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:33 +msgid "" +"Each entry displays the total amount paid for each specific type of salary " +"attachment, for each employee." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "" +"The Attachment of Salary report that shows all salary garnishments in a " +"condensed view." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:39 +msgid "" +"The report can be downloaded as an XLSX file, or :doc:`inserted into a " +"spreadsheet <../../productivity/spreadsheet/insert>` using the corresponding" +" buttons at the top." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:42 +msgid "" +"Click the :guilabel:`Measures` button to reveal the options of what data is " +"displayed. :guilabel:`Assignment of salary`, :guilabel:`Attachment of " +"salary`, and :guilabel:`Child support` are all selected and visible, by " +"default, while the :guilabel:`Count` option is not." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:46 +msgid "" +"Click an option to either show or hide that particular metric. A :icon:`fa-" +"check` :guilabel:`(checkmark)` icon indicates the data is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:50 +msgid "Compare to previous year" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:52 +msgid "" +"The :guilabel:`Salary Attachment Report` can be compared to the report for " +"the previous time period or the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:55 +msgid "" +"To view these comparisons, click the :icon:`fa-caret-down` :guilabel:`(down " +"arrow)` icon in the search bar, then click either :guilabel:`Payslip End " +"Date: Previous Period` or :guilabel:`Payslip End Date: Previous Year`, " +"beneath the :icon:`fa-adjust` :guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:59 +msgid "" +"The report updates and displays the current time period values, and the " +"previous time period values, as well as the :guilabel:`Variation` between " +"the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachment.rst:-1 +msgid "The salary attachment report modified to compare to the previous year." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:5 +msgid "" +"Salary attachments are portions of earnings taken directly out of a payslip " +"for a specific purpose, whether voluntary or required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:8 +msgid "" +"When the deduction is voluntary, they are typically considered *deductions*." +" When the deduction is court-ordered, or involuntary, it is sometimes " +"referred to as a *wage garnishment*. In Odoo, these are all universally " +"called, *salary attachments*." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:12 +msgid "" +"Note that salary attachments could also be used to give recurring amount of " +"money to employees. Like bonus divided in multiple parts." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:18 +msgid "Salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:20 +msgid "" +"To view the currently configured salary attachment types, navigate to " +":menuselection:`Payroll app --> Configuration --> Salary Attachment Types`. " +"The default salary attachment types are: :guilabel:`Attachment of Salary`, " +":guilabel:`Assignment of Salary`, and :guilabel:`Child Support`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:24 +msgid "" +"Each salary attachment type displays the :guilabel:`Name` of the attachment " +"type, the :guilabel:`Code` used when calculating payslips, a checkbox to " +"indicate if there is :guilabel:`No End Date`, and whether it is " +":guilabel:`Country` specific (or universal)." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The default salary attachment types." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:32 +msgid "Create new salary attachment types" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:35 +msgid "" +"Upon installation of the **Payroll** application, the pre-configured default" +" salary attachment types are linked to a variety of rules that are linked to" +" various salary structures, as well as the installed :ref:`localization " +"package `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:39 +msgid "" +"It is **not** recommended to alter or modify **any** of the preconfigured " +"salary attachment types, especially if they have been previously used on " +"payslips in the database. Doing so may affect various salary rules, and can " +"prevent the creation of payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:43 +msgid "" +"A new salary attachment type *can* be created, but this should only be done " +"when absolutely necessary. A salary attachment type needs to be linked to a " +"salary rule in order to be considered in the salary computation." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:47 +msgid "" +"To make a new type of salary attachment, click the :guilabel:`New` button, " +"and a blank :guilabel:`Salary Attachment Types` form loads. Enter the " +":guilabel:`Name` for the new salary attachment type in the corresponding " +"field. Next, enter the :guilabel:`Code` used in the salary rules to compute " +"payslips. Last, tick the :guilabel:`No End Date` checkbox if this salary " +"attachment never expires." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:53 +msgid "" +"If in a multi-company database, with locations in multiple countries, a " +":guilabel:`Country` field also appears on the :guilabel:`Salary Attachment " +"Types` form. Select the country the attachment applies to, or leave blank if" +" it is universal." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:60 +msgid "Create a salary attachment" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:62 +msgid "" +"All salary attachments must be configured separately for each employee, for " +"each type of salary attachment. To view the currently configured salary " +"attachments, navigate to :menuselection:`Payroll app --> Contracts --> " +"Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:66 +msgid "" +"All salary attachments appear in a default list view, and displays the name " +"of the :guilabel:`Employees`, :guilabel:`Description`, the salary attachment" +" :guilabel:`Type`, the :guilabel:`Monthly Amount`, :guilabel:`Start Date`, " +"and current :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:70 +msgid "" +"To create a new salary attachment, click the :guilabel:`New` button in the " +"top-left corner, and a blank :guilabel:`Salary Attachment` form loads. Enter" +" the following information on the form:" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:73 +msgid "" +":guilabel:`Employees`: Using the drop-down menu, select the desired " +"employees. Multiple employees can be listed in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:75 +msgid "" +":guilabel:`Description`: Enter a short description of the salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:76 +msgid "" +":guilabel:`Type`: Using the drop-down menu, select the specific :ref:`salary" +" attachment type `." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:78 +msgid "" +":guilabel:`Start Date`: Using the calendar selector, select the date the " +"salary attachment goes into effect." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:80 +msgid "" +":guilabel:`Estimated End Date`: This field is **not** modifiable, and " +"**only** appears after the :guilabel:`Monthly Amount` field is populated. " +"This field is the estimated date when the salary attachment will be " +"completed. Today's date populates the field by default. Then, when the " +":guilabel:`Total Amount` field is populated, this date is updated." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:84 +msgid "" +":guilabel:`Document`: If any documentation is needed, such as a court order," +" click the :guilabel:`Upload your file` button, and a file explorer window " +"loads. Select the desired document to attach it to the record. Only **one** " +"document can be attached to a salary attachment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:87 +msgid "" +":guilabel:`Monthly Amount`: Enter the amount taken out of each paycheck " +"every month in this field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:88 +msgid "" +":guilabel:`Total Amount`: This field **only** appears if the :ref:`salary " +"attachment type ` has no end date (the " +":guilabel:`No End Date` option is **not** ticked.)" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:-1 +msgid "The salary attachment form with all fields filled out." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:95 +msgid "" +"Since the salary attachment form auto saves as the fields are populated, " +"after making a salary attachment for an individual employee, there is no " +"further action required." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:98 +msgid "" +"If creating salary attachments for multiple employees on a single salary " +"attachment form, after the form is filled out, click the :guilabel:`Create " +"Individual Attachments` button. This creates separate salary attachments for" +" each of the employees listed in the :guilabel:`Employees` field." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:102 +msgid "" +"After the separate salary attachments have been created, the screen returns " +"to the :guilabel:`Salary Attachment` dashboard, but with a " +":guilabel:`Description` filter, populated with the description filled in on " +"the salary attachment form. All the salary attachments have a status of " +":guilabel:`Running`, since they are currently active. Clear the filter in " +"the search box to view the default :guilabel:`Salary Attachment` dashboard " +"in its entirety." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:109 +msgid "Manage salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:111 +msgid "" +"Salary attachments can have one of three statuses: *Running*, *Completed*, " +"or *Cancelled*. To view the current status of all salary attachments, " +"navigate to :menuselection:`Payroll app --> Contracts --> Salary " +"Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:115 +msgid "" +"All salary attachments appear in the order they were configured. To view the" +" salary attachments by a particular metric, such as the :guilabel:`Status`, " +"or :guilabel:`Type`, click on the column title to sort by that specific " +"column." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:120 +msgid "Completed salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:122 +msgid "" +"When a salary attachment is created, it has a status of :guilabel:`Running`." +" Once the salary attachment is finished (the *Total Amount* entered on the " +":ref:`salary attachment form ` has been " +"paid in full), the status automatically changes to *Completed*, and the " +"employee no longer has the money taken out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:127 +msgid "" +"If a salary attachment has been fulfilled, but has not automatically changed" +" to *Completed*, the record can be manually updated. To change the status, " +"open the *Salary Attachment* dashboard by navigating to " +":menuselection:`Payroll app --> Contracts --> Salary Attachments`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:131 +msgid "" +"Click on the record to update, and the detailed :guilabel:`Salary " +"Attachment` form loads. On the individual :guilabel:`Salary Attachment` " +"record, click the :guilabel:`Mark as Completed` button in the upper-left " +"corner, and the status changes to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:136 +msgid "" +"The following is an example of when a payroll manager may need to manually " +"change a salary attachment from :guilabel:`Active` to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:139 +msgid "" +"Rose Smith has a salary attachment for a lawsuit settlement, where she is " +"required to pay $3,000.00. A salary attachment is created that takes $250.00" +" a month out of Rose's paycheck, to go towards this settlement payment." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:143 +msgid "" +"After six months, Rose has paid $1,500.00 from her salary. She received a " +"tax refund, and uses the money to pay off the remainder of the lawsuit " +"settlement. After sending the relevant documentation to the payroll manager," +" showing the settlement has been paid in full, the payroll manager manually " +"changes the status of her salary attachment to :guilabel:`Completed`." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:149 +msgid "Cancel salary attachments" +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:151 +msgid "" +"Any salary attachment can be cancelled at any time. To cancel a salary " +"attachment, click on the individual attachment record from the main " +":guilabel:`Salary Attachment` dashboard to open the record. From the " +":guilabel:`Salary Attachment` record, click the :guilabel:`Cancel` button to" +" cancel the salary attachment, and stop having the designated money taken " +"out of future paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/salary_attachments.rst:157 +msgid ":doc:`salary_attachment`" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:5 +msgid "" +"Work entries are created automatically in the *Payroll* app, based on the " +"employee's :ref:`salary structure type `, and from " +"the *Planning*, *Attendances*, and *Time Off* applications." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:9 +msgid "" +"The *Work Entries* dashboard of the *Payroll* application provides a visual " +"overview of the individual work entries for every employee." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:12 +msgid "" +"To open the dashboard, navigate to :menuselection:`Payroll app --> Work " +"Entries --> Work Entries`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:14 +msgid "" +"On the :guilabel:`Work Entry` dashboard, work entries appear in alphabetical" +" order, based on the first name of the employees. The entire month is " +"displayed, with the current day highlighted in pale yellow." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:18 +msgid "" +"If any entries have :ref:`conflicts ` that need to be " +"resolved, the dashboard defaults to filter only the :guilabel:`Conflicting` " +"entries." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:21 +msgid "" +"To remove the filter from the :guilabel:`Search...` bar to view all work " +"entries, click the :guilabel:`✖️ (remove)` icon on the " +":guilabel:`Conflicting` filter in the :guilabel:`Search...` bar, and all " +"work entries appear in the list." +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:31 +msgid "" +"To change the view, so only the entries for a single day, week, or month are" +" shown, click on :guilabel:`Month`. A drop-down menu appears with the " +"options of :guilabel:`Day`, :guilabel:`Week`, or :guilabel:`Month`. Click on" +" one of the options to only display data for that specific selection." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:35 +msgid "" +"Use the :guilabel:`⬅️ (left arrow)` and :guilabel:`➡️ (right arrow)` icons " +"on the left and right side of the :guilabel:`Month` button to adjust the " +"displayed dates. The arrows adjust the date based on the type of time " +"selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:39 +msgid "" +"For example, if :guilabel:`Month` is selected, the arrows move one month " +"with each click of the arrow. If :guilabel:`Week` or :guilabel:`Day` is " +"selected, the time moves by either a week or a day for each click of the " +"arrow, respectively." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:43 +msgid "" +"At any point, to return to a view containing the current day, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:48 +msgid "Add a new work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:50 +msgid "" +"If a work entry is missing and needs to be added, such as sick time, or if " +"an employee forgot to clock in and out for a shift, click :guilabel:`New` on" +" the :guilabel:`Work Entry` dashboard, to create a new work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:54 +msgid "A :guilabel:`Create` work entry pop-up form appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:58 +msgid "" +":guilabel:`Description`: enter a short description for the work entry, such " +"as `Sick Time`. If this field is left blank, it automatically populates once" +" an employee is selected. The default entry is `Attendance: (Employee)`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:61 +msgid "" +":guilabel:`Employee`: select the employee the work entry is for, using the " +"drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:62 +msgid "" +":guilabel:`Work Entry Type`: select the :ref:`work entry type ` using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:64 +msgid "" +":guilabel:`From` and :guilabel:`To`: enter the start (:guilabel:`From`) and " +"end (:guilabel:`To`) dates and times for the work entry." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:67 +msgid "" +"First, click on either the :guilabel:`From` or :guilabel:`To` line to reveal" +" a calendar pop-up window. 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:71 +msgid "" +"Next, select the time, by clicking on either the hour or minute fields at " +"the bottom of the calendar, and select the desired time for both the hour " +"and minutes." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:74 +msgid "" +"When the date and time are correct for the entry, click the " +":guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:75 +msgid "" +":guilabel:`Duration`: displays the hours based on the :guilabel:`To` and " +":guilabel:`From` entries. Modifying this field modifies the :guilabel:`To` " +"field (the :guilabel:`From` field does not change)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:79 +msgid "" +"Once the desired information is entered, click :guilabel:`Save & Close` to " +"save the entry, and close the pop-up form." +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:89 +msgid "Conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:91 +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:95 +msgid "" +"Any work entry that has a conflict to be resolved is indicated on the main " +":guilabel:`Work Entry` dashboard, which can be accessed by navigating to " +":menuselection:`Payroll app --> Work Entries --> Work Entries`. Only " +"conflicts needing resolution are shown by default." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:99 +msgid "" +"Conflicts are indicated with an orange triangle in the top-left corner of " +"each individual work entry. Click on an individual work entry to see the " +"date and time for the specific work entry, then click :guilabel:`Edit` to " +"view the conflict details in a pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "A row of conflicts, with one entry showing details for the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:107 +msgid "" +"The conflict is briefly explained in an orange text box in the " +":guilabel:`Open` pop-up window that appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:110 +msgid "" +"The :guilabel:`Description`, :guilabel:`Employee`, and :guilabel:`Work Entry" +" Type` are listed on the left side of the pop-up window. The " +":guilabel:`From` and :guilabel:`To` date and time range, as well as the " +"total time (in hours) in the :guilabel:`Duration` field, appears on the " +"right side." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:114 +msgid "" +"If the conflict is due to a time off request that has not been approved yet," +" a :guilabel:`Time Off` field appears on the left side, with the type of " +"time off requested in the description." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed conflict pop-up window that appears when Edit is clicked." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:122 +msgid "Time off conflicts" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:124 +msgid "" +"The most common work entry conflicts are for time off requests that have " +"been submitted, but not yet approved, which results in duplicate work " +"entries for that employee (one for time off and another for regular work)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:128 +msgid "" +"If there is a conflict because a time off request is in the system for the " +"same time that a regular work entry already exists, the time off request is " +"entered in the :guilabel:`Time Off` field." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:131 +msgid "" +"The time off conflict can be resolved either on the work entry pop-up " +"window, or on a detailed time off request pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:135 +msgid "Resolve on work entry" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:137 +msgid "" +"To resolve the time off conflict on this work entry pop-up window, click the" +" :guilabel:`Approve Time Off` button to approve the time off request, and " +"resolve the work entry conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:140 +msgid "" +"The :guilabel:`Approve Time Off` and :guilabel:`Refuse Time Off` buttons " +"disappear. Click the :guilabel:`Save & Close` button to close the pop-up " +"window. The conflict disappears from the :guilabel:`Work Entry` dashboard, " +"since the conflict is resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:145 +msgid "Resolve on time off request" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:147 +msgid "" +"To resolve the time off conflict on the detailed time off request pop-up " +"window, click the :guilabel:`Internal Link` button at the end of the " +":guilabel:`Time Off` entry line, and the time off request details appear in " +"a new pop-up window. The request can be modified, if needed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:151 +msgid "" +"Click the :guilabel:`Approve` button to approve the request, then click the " +":guilabel:`Save & Close` button to save the changes, and go back to the work" +" entry conflict pop-up window." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "The detailed time off request form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:158 +msgid "" +"Now, the :guilabel:`Approve Time Off` button is hidden, only the " +":guilabel:`Refuse Time Off` button is visible." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:161 +msgid "" +"If the approval was a mistake, the request can be refused here, by clicking " +"the :guilabel:`Refuse Time Off` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:164 +msgid "" +"Since the time off was approved in the time off window, click the " +":guilabel:`X` in the top-right corner to close the window. The conflict " +"disappears from the :guilabel:`Work Entry` dashboard, since it has been " +"resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:171 +msgid "Regenerate work entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:173 +msgid "" +"When regenerating work entries, any manual changes, such as resolved " +"conflicts, are overwritten, and work entries are regenerated (or recreated) " +"from the applications that created them." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:176 +msgid "" +"This method for correcting a large amount of conflicts is recommended to " +"keep all records correct. While :ref:`conflicts ` *can* " +"be resolved individually, if the conflicts are caused from another " +"application, it is best practice to ensure the records in the other " +"applications are also correct. That is why it is recommended to resolve " +"these conflicts in the applications that created the conflict." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:182 +msgid "" +"Another reason this method is recommended is because, when work entries are " +"regenerated, the conflicts reappear, if the issue in the related application" +" is **not** resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:185 +msgid "" +"First, ensure the issues are resolved in the specific applications that " +"caused the work entry conflicts." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:188 +msgid "" +"Next, click the :guilabel:`Regenerate Work Entries` button at the top of the" +" :guilabel:`Work Entries` dashboard, and a :guilabel:`Work Entry " +"Regeneration` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:191 +msgid "" +"Select the :guilabel:`Employees` to regenerate work entries for from the " +"drop-down menu, and adjust the :guilabel:`From` and :guilabel:`To` fields, " +"so the correct date range is displayed." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:194 +msgid "" +"Click the :guilabel:`Regenerate Work Entries` button, and the work entries " +"are recreated. Once finished, the pop-up window closes." +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:202 +msgid "" +"An employee has incorrect work entries generated from the *Planning* app " +"because they were incorrectly assigned to two work stations simultaneously. " +"This should be fixed in the *Planning* app, instead of the *Payroll* app." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:206 +msgid "" +"To correct this issue, modify the employee's schedule in the *Planning* app," +" so they are correctly assigned to only one work station. Then, in the " +"*Payroll* app, regenerate work entries for that employee, for that specific " +"time period." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:210 +msgid "" +"The *Payroll* app then pulls the new, corrected data form the *Planning* " +"app, and recreates the correct work entries for that employee. All conflicts" +" for that employee are now resolved." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:214 +msgid "Generating payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:216 +msgid "" +"To generate payslips, :ref:`navigate to the time period ` the payslips should be generated for. Ensure the " +":guilabel:`Conflicting` filter is removed. When the desired pay period is " +"displayed, click the :guilabel:`Generate Payslips` button." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:221 +msgid "" +"If the :guilabel:`Generate Payslips` button is not active (appears pale " +"purple, instead of dark purple), that indicates there are conflicts, or the " +"date selected includes dates in the future. Resolve all conflicts before " +"generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:225 +msgid "" +"When the :guilabel:`Generate Payslips` button is clicked, a batch entry " +"appears on a separate page for the time period selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:228 +msgid "" +"The batch name populates the :guilabel:`Batch Name` field in a default `From" +" (date) to (date)` format." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:231 +msgid "" +"The date range to which the payslips apply appears in the :guilabel:`Period`" +" field, and the company appears in the :guilabel:`Company` field. It is " +"**not** possible to make changes to this form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:234 +msgid "" +"Click the :guilabel:`Create Draft Entry` button to create the payslips for " +"the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:236 +msgid "" +"Click the :guilabel:`Payslips` smart button at the top of the page to view " +"all the payslips for the batch." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "Information that appears when generating payslips." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:244 +msgid "Printing payslips" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:246 +msgid "" +"To print payslips, first view the individual payslips by clicking the " +":guilabel:`Payslips` smart button on the batch form." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:249 +msgid "" +"Next, select the payslips to print from the :guilabel:`Payslips` list. Click" +" the box next to each payslip to print, or click the box to the left of the " +":guilabel:`Reference` column title, to select all the payslips in the list " +"at once." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:253 +msgid "" +"Click the :guilabel:`Print` button, and a PDF file is 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:260 +msgid "" +"The :guilabel:`Print` button does **not** appear until at least one payslip " +"is selected in the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:264 +msgid "Time off to report" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:266 +msgid "" +"If a time off request is submitted for a time period that was already " +"processed on a payslip, the time off request appears in the *Time Off* page " +"in the *Payroll* app, which is accessible by navigating to " +":menuselection:`Payroll app --> Work Entries --> Time Off to Report`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:270 +msgid "" +"On the :guilabel:`Time Off` page, the request appears with a status of " +":guilabel:`To defer to next payslip`. This is because the employee was " +"already paid for that day, and it was logged as time spent at work, as a " +"typical work day." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:274 +msgid "" +"In order to keep the employee's time off balances correct, the time off " +"request **must** be applied to the following pay period. This not only " +"ensures time off request balances are current, it also eliminates the need " +"to redo work entries, cancel paychecks, and reissue paychecks." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:278 +msgid "" +"The most common scenario when this situation occurs, is when payslips are " +"processed a day or two before the pay period ends, and an employee is " +"unexpectedly sick on one of the last days of the pay period. The employee " +"puts in a time off request for a day that was already processed on a payslip" +" as a regular work day. Instead of cancelling the payslip, modifying the " +"work entries, and reissuing the paycheck, Odoo allows for those time off " +"requests to be applied to the following pay period, instead." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:285 +msgid "" +"To view all the time off requests that need to be deferred to the next " +"payslip, navigate to :menuselection:`Payroll app --> Work Entries --> Time " +"Off to Report`. The default filter for this report is :guilabel:`To Defer`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:289 +msgid "" +"All time off requests that need to be applied to the following pay period " +"appear with a :guilabel:`Payslip State` of :guilabel:`To defer to next " +"payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"A list of all time off requests that were not approved before payslips were " +"generated." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:297 +msgid "Defer multiple time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:299 +msgid "" +"To select the work entries to defer, click the box to the left of the work " +"entry line. To select all work entries in the list, click the box to the " +"left of the :guilabel:`Employees` column title, at the top of the list." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:303 +msgid "" +"Once any work entry is selected, two buttons appear at the top of the " +"report: a :guilabel:`(#) Selected` button, and an :guilabel:`Actions` " +"button. The :guilabel:`(#) Selected` button indicates how many entries are " +"currently selected." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:307 +msgid "" +"When all the desired work entries are selected, click the " +":guilabel:`Actions` button, and a menu appears with several choices. Click " +":guilabel:`Defer to Next Month` in the list, and all selected entries are " +"deferred to the following month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The actions button and # Selected buttons that appear after any selections " +"are made." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:316 +msgid "Defer individual time off entries" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:318 +msgid "" +"Time off requests appearing on the :guilabel:`Time Off to Report` list can " +"be deferred individually." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:320 +msgid "" +"Click on an individual time off request, and the details for that request " +"load." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:322 +msgid "" +"The specific details for the time off request appear on the left-hand side, " +"and all of the employee's submitted time off requests appear on the right-" +"hand side (including the request in the details on the left-hand side)." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:326 +msgid "" +"To defer the time off request to the next payslip, click the " +":guilabel:`Report to Next Month` button at the top. Once processed, the " +":guilabel:`Report to Next Month` button disappears, and the " +":guilabel:`Payslip State` changes from :guilabel:`To defer to next payslip` " +"to :guilabel:`Computed in Current Payslip`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:331 +msgid "" +"To go back to the :guilabel:`Time Off to Report` list, click on " +":guilabel:`Time Off` in the breadcrumb menu." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:-1 +msgid "" +"The time off details for an individual request that needs to be deferred." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entries.rst:339 +msgid ":ref:`Configure work entries `" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:3 +msgid "Work entry analysis" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:5 +msgid "" +"The default *Work Entries Analysis* report provides an overview of the " +"validated work entries for the current month. To view this report, navigate " +"to :menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:9 +msgid "" +"The work entries appear in a pivot table, with the default filters of " +":guilabel:`Current month: (Month)(Year)` and :guilabel:`Validated`. The " +"various types of :doc:`work_entries` populate the rows, while the " +":guilabel:`Total` values populate the only visible column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:13 +msgid "" +"To change the displayed information, click :icon:`fa-plus-square` " +":guilabel:`Total` above the main column, revealing a drop-down menu of " +"available metrics. Click on one of the available groupings, and the data is " +"further organized by that selected metric. The default options are " +":guilabel:`Work Entry Type`, :guilabel:`Employee`, and " +":guilabel:`Department`. If in a multi-company database, a " +":guilabel:`Company` option also appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:20 +msgid "Work entry analysis comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:22 +msgid "" +"It is possible to compare the work entries from one time period to a " +"previous time period. To view this comparison, first navigate to " +":menuselection:`Payroll app --> Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:26 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-adjust` " +":guilabel:`Comparison` section, click on either :guilabel:`Current Month: " +"Previous Period` or :guilabel:`Current Month: Previous Year`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:30 +msgid "" +"The report updates and displays the data for the current time period, data " +"for the selected previous time period, as well as the :guilabel:`Variation` " +"between the two, in a percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the work entries of the current month and the " +"previous month." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:37 +msgid "" +"If no work entries for a specific :ref:`work entry type ` are logged for the time period, it does **not** appear on the " +"report. That does **not** mean the work entry type does not exist, or is not" +" configured." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:41 +msgid "" +"Additionally, if the default :guilabel:`Current month: (Month)(Year)` filter" +" is removed from the search bar, the :guilabel:`Comparison` column does " +"**not** appear; there must be a time-frame selected to view the " +":guilabel:`Comparison` column." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:46 +msgid "Use case: overtime report comparison" +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:48 +msgid "" +"It is possible to alter the *Work Entries Analysis* report to show a " +"comparison of only overtime work entries, grouped by employee, for a " +"specific time period. To view this data, first navigate to the default *Work" +" entry analysis* report by going to :menuselection:`Payroll app --> " +"Reporting --> Work Entry Analysis`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:53 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` icon in the " +"search bar, revealing a drop-down menu. Under the :icon:`fa-filter` " +":guilabel:`Filters` column, click :guilabel:`Add Custom Filter`, and a " +":guilabel:`Add Custom Filter` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:57 +msgid "" +"Using the drop-down menu, select :guilabel:`Work Entry Type` for the first " +"field, leave the middle field as-is (with :guilabel:`is in` populating the " +"field), and select :guilabel:`Overtime Hours` for the last field. Click " +":guilabel:`Add`, and all other work entry types disappear, and " +":guilabel:`Overtime Hours` appear in the sole row." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:62 +msgid "" +"To compare overtime from the current month to the previous month, to see " +"which month had more overtime logged, click the :icon:`fa-caret-down` " +":guilabel:`(down arrow)` icon again in the search bar. Under the :icon:`fa-" +"adjust` :guilabel:`Comparison` section, click :guilabel:`Current Month: " +"Previous Period`. Click away from the drop-down menu to close it." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:67 +msgid "" +"Now, the report displays the :guilabel:`Overtime Hours` for the current " +"month and the previous month, along with the :guilabel:`Variation`, in a " +"percentage." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:70 +msgid "" +"To view which employees received the most overtime, click :icon:`fa-plus-" +"square` :guilabel:`Overtime Hours`, revealing a drop-down menu of options. " +"Click :guilabel:`Employee`, and all employees with overtime work entries for" +" either the current or previous month appears." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:74 +msgid "" +"In this example, it can be determined that :guilabel:`Marc Demo` worked the " +"most overtime in :guilabel:`August 2024`, whereas :guilabel:`Beth Evans` " +"worked the most overtime hours in :guilabel:`September 2024`. Additionally, " +":guilabel:`Mitchell Admin` had the largest variation change, with a " +":guilabel:`-100%` change from :guilabel:`August 2024` to " +":guilabel:`September 2024`." +msgstr "" + +#: ../../content/applications/hr/payroll/work_entry_analysis.rst:-1 +msgid "" +"A pivot table comparing the overtime from September 2024 with August 2024." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:5 +msgid "Recruitment" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:7 +msgid "" +"Odoo keeps all job applicants organized with a preconfigured series of steps" +" and stages that each applicant goes through. Each stage has a specific " +"steps that should be performed. These range from scheduling a phone call, " +"conducting an interview, or sending a job offer, for example. This process " +"is referred to as the *applicant flow.*" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:12 +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:16 +msgid "" +":ref:`Stages can be configured ` so that an email" +" is automatically sent out using a set, preconfigured 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:20 +msgid "" +"The flow described in this document is Odoo's default configuration, but it " +"can be customized to suit any recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:24 +msgid "" +"Stages apply to all job positions unless :ref:`marked as job-specific " +"` Changes to stages (e.g., additions, " +"deletions) affect all positions unless explicitly scoped." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:33 +msgid "" +"Before creating a job position in Odoo, configure the necessary settings for" +" the **Recruitment** app. To view and edit the settings, navigate to " +":menuselection:`Recruitment app --> Configuration --> Settings`. After any " +"changes are made, click the :guilabel:`Save` button in the top-left corner " +"to save all the changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:39 +msgid "Job posting" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:41 +msgid "" +"The :guilabel:`Job Posting` section of the **Recruitment** app settings has " +"two configurations, enabling posting jobs on the company website, and on " +"external job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:44 +msgid "" +"If job positions are to be posted to the company's website, enable the " +":guilabel:`Online Posting` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:48 +msgid "" +"The :guilabel:`Online Posting` is only available if the :doc:`Website " +"<../websites/website>` application is also installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:51 +msgid "" +"The **Recruitment** app can post job positions directly to a job board. To " +"enable this, click :icon:`oi-arrow-right` :guilabel:`Choose a Job Board`, " +"and the required module is presented, if not already installed. Click " +":guilabel:`Install` on the corresponding module, then the main Odoo " +"dashboard loads after a successful installation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:56 +msgid "" +"Open the **Recruitment** app, and navigate to :menuselection:`Recruitment " +"app --> Configuration --> Settings`. The corresponding job board credentials" +" are listed. Enter the :guilabel:`Username` and :guilabel:`Password` for the" +" job board. Click the :guilabel:`Save` button after making any changes." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:61 +msgid "Currently, the only job board integration with Odoo is Monster.com." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:64 +msgid "Process" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:66 +msgid "" +"The :guilabel:`Process` section of the settings page specifies what the " +"database can and cannot do during the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:70 +msgid "Send interview survey" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:72 +msgid "" +"Odoo is capable of having a survey sent to an applicant to gather more " +"information about them. Surveys can be thought of as exams, or " +"questionnaires, and can be customized in various ways to provide the " +"recruitment team with valuable insights into the applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:76 +msgid "" +"Enable the :guilabel:`Send Interview Survey` option to send surveys to " +"applicants. Once enabled, an :icon:`fa-arrow-right` :guilabel:`Interview " +"Survey` internal link appears. Click the :icon:`fa-arrow-right` " +":guilabel:`Interview Survey` link to navigate to a list of all created " +"surveys." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:81 +msgid "" +"This list includes all surveys that were created in the database, not only " +"surveys used in the **Recruitment** app. If no surveys have been created, " +"the surveys list displays a :guilabel:`No Survey Found` message, and " +"presents options to create a survey from several preconfigured survey " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:87 +msgid ":doc:`create/edit surveys <../marketing/surveys/create>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:90 +msgid "" +"Enabling the :guilabel:`Send Interview Survey` option will install the " +"**Surveys** application once the settings are saved, if not already " +"installed." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:96 +msgid "" +"When sending an offer to an applicant, an expiration date can be set on the " +"offer. Enter the number of days an offer is valid for in the " +":guilabel:`days` field. After the set amount of days has passed, if the " +"applicant has not accepted the offer, the offer is no longer available." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:103 +msgid "Résumé display" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:105 +msgid "" +"When applicants submit an application, one of the default required fields is" +" a résumé, or :abbr:`CV (curriculum vitae)`. All résumés are stored in the " +"**Documents** application, and are accessible on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:109 +msgid "" +"A résumé has the option to appear on the applicant's form, which can be " +"viewed by clicking on the applicant's card. The résumé appears on the right-" +"side of the screen. If this is not enabled, the résumé is accessed via a " +"link in the chatter, where it needs to be clicked to expand and view it, or " +"downloaded." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:114 +msgid "" +"Enable the :guilabel:`Résumé Display` option to show the résumé on the " +"applicant's card by default, and in addition to the document link. When " +"enabled, the résumé appears on the right side of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:119 +msgid "" +"For the résumé to appear on the right-side, the browser window must be in " +"full-screen mode (where the browser spans the entire screen)." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:122 +msgid "" +"If the browser window is set to a size smaller than the entire width of the " +"screen (not full-screen), then the résumé does not appear on the right-side." +" Instead, the résumé appears in the :guilabel:`Files` section of the " +"chatter, below the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The résumé on an applicant's card, appearing on the right side." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:130 +msgid "In-App Purchases" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:132 +msgid "" +"The :guilabel:`In-App Purchases` section of the :guilabel:`Settings` menu " +"deals with items that required credits to use, such as :abbr:`SMS (Short " +"Message Service)` text messages, and digitizing résumés." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:137 +msgid "" +":doc:`SMS pricing and FAQs <../marketing/sms_marketing/pricing_and_faq>`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:140 +#: ../../content/applications/hr/referrals/share_jobs.rst:82 +msgid "Send SMS" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:142 +msgid "" +"It is possible to send text messages to applicants directly through the " +"**Recruitment** app. This feature requires credits to use. Click the " +":icon:`fa-arrow-right` :guilabel:`Manage Service & Buy Credits` internal " +"link, and follow the steps to :doc:`purchase credits " +"<../marketing/sms_marketing/pricing_and_faq>`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:150 +msgid "Résumé digitization (OCR)" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:152 +msgid "" +"When an application is submitted using any of the available methods, such as" +" an online application submission, emailing a resume to the job position " +"alias, or creating an applicant record directly from the database, it is " +"possible to have Odoo extract the applicant's name, phone number, and email " +"address from the résumé and populate the applicant's form. To do so, enable " +"the :guilabel:`Résumé Digitization (OCR)` option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:158 +msgid "" +"When enabled, additional options appear. Click on the corresponding radio " +"button to select one of the following options:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:161 +msgid "" +":guilabel:`Do not digitize`: this option turns off résumé digitization." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:162 +msgid "" +":guilabel:`Digitize on demand only`: this option only digitizes resumes when" +" requested. A :guilabel:`Digitize document` buttons appears on applicant " +"cards. When clicked, the résumé is scanned and the applicant's card is " +"updated." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:165 +msgid "" +":guilabel:`Digitize automatically`: this option automatically digitizes all " +"résumés when they are submitted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:168 +msgid "" +"Beneath these options are two additional links. Click the :icon:`fa-arrow-" +"right` :guilabel:`Manage Service & Buy Credits` internal link to purchase " +"credits for résumé digitization. Click the :icon:`fa-arrow-right` " +":guilabel:`View My Services` internal link to view a list of all current " +"services, and their remaining credit balances." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:173 +msgid "" +"For more information on document digitization and :abbr:`IAP's (in-app " +"purchases)`, refer to the :doc:`In-app purchase (IAP) " +"<../essentials/in_app_purchase>` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:177 +msgid "" +"The :guilabel:`Do not digitize` option may appear redundant but serves a " +"distinct purpose. Disabling the :guilabel:`Résumé Digitization (OCR)` option" +" uninstalls the module, while :guilabel:`Do not digitize` keeps the module " +"installed but inactive—allowing the user to re-enable digitization later " +"without reinstalling the module." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:185 +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:193 +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. In Odoo, six default stages are configured:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:197 +msgid ":ref:`New `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:198 +msgid ":ref:`Initial Qualification `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:199 +msgid ":ref:`First Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:200 +msgid ":ref:`Second Interview `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:201 +msgid ":doc:`Contract Proposal `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:202 +msgid "" +":ref:`Contract Signed `" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:204 +msgid "" +"The last column, :guilabel:`Contract Signed`, is folded by default. Folded " +"columns appear 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:212 +msgid "" +"Each stage has a color-coded bar beneath the stage name, providing status " +"information for the applicant's in that specific stage. The status colors " +"are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:215 +msgid ":guilabel:`Green`: the applicant is ready to move to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:216 +msgid "" +":guilabel:`Red`: the applicant is blocked from moving to the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:217 +msgid "" +":guilabel:`Gray`: the applicant is still in progress in the current stage " +"and is neither ready nor blocked from the next stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:220 +msgid "" +"The status for each card is set manually. To set the status, click on the " +"small circle in the lower-left of the applicant card. A status pop-up window" +" appears. Click on the desired status for the applicant. The status dot on " +"the applicant card as well as the status bar updates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The applicant card statuses, and status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:228 +msgid "" +"The names for the three status colors (`In Progress`, `Ready for Next " +"Stage`, and `Blocked`) :ref:`can be modified `, " +"if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:234 +msgid "Customize stages" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:236 +msgid "" +"Stages can be modified, added, or deleted to match the particular hiring " +"steps of a business." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:239 +msgid "New stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:241 +msgid "" +"To create a new stage, click on :icon:`fa-plus` :guilabel:`Stage` and a new " +"column appears. Enter the title for the new stage in the :guilabel:`Stage " +"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 stage creation." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "The plus sign to click to add a new column to the Kanban stages." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:252 +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:215 +msgid "Modify stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:254 +msgid "" +"To modify the settings of a stage, hover over the name of the stage, and a " +":icon:`fa-cog` :guilabel:`(Settings)` icon appears in the upper right hand " +"side of the stage. Click on the :icon:`fa-cog` :guilabel:`(Settings)` icon " +"and a menu appears. Then click on the :guilabel:`Edit` option. An " +":guilabel:`Edit: (Stage)` form appears. Make any desired modifications to " +"the form, then click :guilabel:`Save & Close` 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:267 +msgid "Edit stage form" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:269 +msgid "" +"The :guilabel:`Edit: (Stage)` form is where the stage's settings are " +"configured. The only required field is the :guilabel:`Stage Name`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:272 +msgid "The fields to be populated or modified are:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:274 +msgid ":guilabel:`Stage Name`: Type in a name for the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:275 +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 is automatically sent to the applicant using the " +"selected template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:278 +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:280 +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:284 +msgid "" +":guilabel:`Job Specific`: If the stage only applies to specific job " +"positions, select the job positions from the drop-down menu. Multiple job " +"positions can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:286 +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. The **Referrals** app" +" must be installed in order to use this option." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:291 +msgid "" +":guilabel:`Points`: If :guilabel:`Show in Referrals` is enabled, this field " +"appears. Enter the number of points the employee earns when an applicant " +"moves to this stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:293 +msgid "" +":guilabel:`Tooltips` section: There are three preconfigured status 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:298 +msgid "" +":guilabel:`Requirements`: Enter any internal notes for this stage explaining" +" any requirements of the stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:302 +msgid "Delete stage" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:304 +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 :icon:`fa-cog` " +":guilabel:`(Settings)` icon appears. First, click on the :icon:`fa-cog` " +":guilabel:`(Settings)` icon to reveal a drop-down menu, then click " +":guilabel:`Delete`. A :guilabel:`Confirmation` pop-up warning appears, " +"asking :guilabel:`Are you sure you want to delete this column?` Click " +":guilabel:`Delete` to delete the column." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:311 +msgid "" +"If there are applicants currently in the stage being deleted, an error pops " +"up when attempting to delete the stage. The records currently in the stage " +"to need to be either deleted, archived, or moved to a different stage before" +" the stage can be deleted." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:316 +msgid "Email templates" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:318 +msgid "" +"To communicate with the applicant, Odoo has several preconfigured email " +"templates that can be used. The preconfigured email templates and when to " +"use them are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:321 +msgid "" +":guilabel:`Recruitment: 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:`New` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:324 +msgid "" +":guilabel:`Recruitment: Interest`: this template is used to let the " +"applicant know that their application caught the recruiter's attention, and " +"they have been shortlisted for either a phone call or an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:327 +msgid "" +":guilabel:`Recruitment: 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:330 +msgid "" +":guilabel:`Recruitment: Refuse`: this template is used when an applicant is " +"no longer being considered for the position." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:332 +msgid "" +":guilabel:`Recruitment: Schedule Interview`: this template is used to let " +"the applicant know that they have passed the :guilabel:`Initial " +"Qualification` stage, and they will soon be contacted to set up an interview" +" with the recruiter. This email is automatically sent out once the applicant" +" is in the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:338 +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/companies/email_template` document." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:341 +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." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +msgid "Send an email from the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:347 +msgid "" +"Click the :icon:`fa-expand` :guilabel:`(Full composer)` icon in the bottom " +"right corner of the :guilabel:`Send Message` tab in the chatter. A " +":guilabel:`Compose Email` pop-up window loads, with the :guilabel:`To` and " +":guilabel:`Subject` pre-populated. The applicant's email address is entered " +"in the :guilabel:`To` field, and the :guilabel:`Subject` is `(Job " +"Position)`. The email body is empty by default." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:353 +msgid "" +"To use a preconfigured email template, click the :icon:`fa-ellipsis-v` " +":guilabel:`(vertical elipsis)` button in the bottom of the window. Select " +"the email template to use from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:357 +msgid "" +"Preconfigured email templates may contain dynamic placeholders so unique " +"information can be populated in the email for a more personalized message to" +" the applicant. Several preconfigured email templates are available to " +"choose from. Depending on the template selected, the email subject or body " +"may change." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:363 +msgid "" +"Only the email templates that are configured for the model load. Other email" +" templates come preconfigured in Odoo, but if they are not configured for " +"the recruitment application, they do not appear in the list of available " +"templates." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:367 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` button at the bottom of the window. Navigate to the " +"file to be attached, then click :guilabel:`Open` to attach it. To delete an " +"attachment, click the :icon:`fa-close` :guilabel:`(delete)` icon to the " +"right of the attachment." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:372 +msgid "" +"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 :icon:`fa-ellipsis-v` :guilabel:`(vertical " +"elipsis)` button in the bottom of the window, and select :guilabel:`Save as " +"Template`. Options are presented to either overwrite an existing template, " +"or save a new template. Click on an existing template name to overwrite that" +" template, or click :guilabel:`Save as Template` to save a new template. A " +":guilabel:`Create a Mail Template` pop-up window loads. Enter a name for the" +" template in the :guilabel:`Template Name` field, then click " +":guilabel:`Save`." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:381 +msgid "" +"To send the email, click :guilabel:`Send` and the email is sent to the " +"applicant. The email then appears in the chatter." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:-1 +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:-1 +msgid "" +"Send a custom survey, also referred to as an interview form, to an applicant using a\n" +"preconfigured template." +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:389 +msgid ":doc:`recruitment/new_job`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:390 +msgid ":doc:`recruitment/add-new-applicants`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:391 +msgid ":doc:`recruitment/schedule_interviews`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:392 +msgid ":doc:`recruitment/offer_job_positions`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:393 +msgid ":doc:`recruitment/refuse_applicant`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:394 +msgid ":doc:`recruitment/applicant_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:395 +msgid ":doc:`recruitment/source_analysis`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:396 +msgid ":doc:`recruitment/time_in_stage`" +msgstr "" + +#: ../../content/applications/hr/recruitment.rst:397 +msgid ":doc:`recruitment/team_performance`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:3 +msgid "Add new applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:5 +msgid "" +"Once an applicant submits an application, either using the online " +"application, or emailing a job position alias, an applicant card is " +"automatically created in the **Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:8 +msgid "" +"However, in some instances, applicants may need to be created manually in " +"the database. This could be necessary if, for example, a company accepts " +"paper applications in the mail, or is meeting prospective applicants at an " +"in-person job fair." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:12 +msgid "" +"To view current applicants, navigate to the :menuselection:`Recruitment` " +"app, then click the desired job position card. Doing so reveals the " +":guilabel:`Applications` page, which displays all applicants for that " +"specific role, in a default Kanban view, organized by stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:16 +msgid "" +"Add new applicants from a job position's :guilabel:`Applications` page by " +"using either: the :ref:`quick add ` button," +" or the :ref:`New ` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:23 +msgid "Quick add" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:25 +msgid "" +"On the :guilabel:`Applications` page, click the quick add button, " +"represented by a small :icon:`fa-plus` :guilabel:`(plus)` icon in the top-" +"right corner of each stage, to add a new applicant to that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:29 +msgid "Enter the following information on the card:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:31 +msgid "" +":guilabel:`Candidate`: Select the applicant from the drop-down menu. " +"Displays as the card title in the Kanban view of the " +":guilabel:`Applications` page. If the candidate is *not* in the system (from" +" a previous application, or is a current employee), after entering the " +"applicant's name, click :guilabel:`Create \"(candidate)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:35 +msgid "" +":guilabel:`Job Position`: 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 appears on the :guilabel:`Applications` page for " +"that newly-selected job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:40 +msgid "" +"After the information is entered, click :guilabel:`Add`. The applicant " +"appears in the list, and a new blank applicant card appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:43 +msgid "" +"If preferred, after entering the :guilabel:`Candidate` in the Kanban card " +"that appears, click :guilabel:`Edit`, and a detailed applicant form loads. " +"Refer to the :ref:`New applicant form ` " +"section for details about filling out the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:47 +msgid "" +"When doing a quick add, clicking away from an empty card, or clicking the " +":icon:`fa-trash-o` (:guilabel:`trash`) icon, discards the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields for a new applicant form entered when using the Quick Add " +"option." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:56 +msgid "New applicant form" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:58 +msgid "" +"On the :guilabel:`Applications` page, click the :guilabel:`New` button in " +"the top-left corner, and a blank application form loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:61 +msgid "" +"On the new application form, the :guilabel:`Job Position` and " +":guilabel:`Recruiter` fields are populated according to the job position " +"configurations, by default. Additionally, the :guilabel:`Department` and " +":guilabel:`Company` fields in the :guilabel:`Details` tab may also be " +"populated, if those details are configured on the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:66 +msgid "" +"Complete the fields in the following sections on the new applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:69 +msgid "" +"Depending on installed applications and configurations, some fields may " +"**not** be displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:74 +msgid "Candidate section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:76 +msgid "" +":guilabel:`Evaluation`: Represents a rating for the applicant: one star " +"(:icon:`fa-star` :icon:`fa-star-o` :icon:`fa-star-o`) is :guilabel:`Good`, " +"two stars (:icon:`fa-star` :icon:`fa-star` :icon:`fa-star-o`) is " +":guilabel:`Very Good`, and three stars (:icon:`fa-star` :icon:`fa-star` " +":icon:`fa-star`)is :guilabel:`Excellent.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:80 +msgid "" +":guilabel:`Candidate`: Enter the applicant's name. This field is displayed " +"as the card title in the Kanban view of the :guilabel:`Applications` page. " +"This is the **only** required field on the form." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:83 +msgid ":guilabel:`Email`: Enter the applicant's email address." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:84 +msgid ":guilabel:`Phone`: Enter the applicant's phone number." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:85 +msgid "" +":guilabel:`LinkedIn Profile`: Enter the web address for the applicant's " +"personal profile on LinkedIn." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:87 +msgid "" +":guilabel:`Job Position`: Select the job position the applicant is applying " +"for. This field is populated by default, but can be changed if necessary." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:89 +msgid "" +":guilabel:`Recruiter`: Select the user responsible for the entire " +"recruitment process for the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:91 +msgid "" +":guilabel:`Interviewers`: Using the drop-down menu, select the people to " +"conduct the interviews. The selected people **must** have either *recruiter*" +" or *officer* rights configured for the **Recruitment** application to " +"appear in the drop-down list. Refer to the :doc:`Access rights " +"<../../general/users/access_rights>` documentation for more information." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:95 +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, then click " +":guilabel:`Create \"new tag\"` from the resulting drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "" +"All the fields of the Candidate section for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:103 +msgid "Notes tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:105 +msgid "" +"Enter any notes regarding the applicant in this tab. These notes are only " +"visible internally, with users that have the proper access rights." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:109 +msgid "Details tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:111 +msgid "" +"The :guilabel:`Details` tab houses various information regarding the " +"applicant and the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:114 +msgid "Applicant section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:116 +msgid "Enter the following information in the respective fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:118 +msgid "" +":guilabel:`Degree`: Select the applicant's highest level of education from " +"the drop-down menu. Options are: :guilabel:`Graduate`, :guilabel:`Bachelor " +"Degree`, :guilabel:`Master Degree`, or :guilabel:`Doctoral Degree`. The " +":guilabel:`Graduate` option indicates the applicant graduated at 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/add-new-applicants.rst:123 +msgid "" +":guilabel:`Availability`: Select the available start date for the applicant." +" To select a date, click on the field to reveal a popover calendar. Use the " +":icon:`fa-angle-left` :guilabel:`(left)` and :icon:`fa-angle-right` " +":guilabel:`(right)` arrows on either side of the month to navigate to the " +"desired month, then click the desired date. Leaving this field blank " +"indicates the applicant can start immediately." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:130 +msgid "Salary package section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:132 +msgid "" +"Configure both the offered and proposed salary and benefits in this section." +" Fill out the following fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:135 +msgid "" +":guilabel:`Expected`: Enter the amount the applicant is requesting 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/add-new-applicants.rst:138 +msgid "" +":guilabel:`Other Benefits`: If any benefits are requested by the applicant, " +"enter them in the blank :guilabel:`Other Benefits` text field to the right " +"of the :guilabel:`Expected` salary field. The benefits should be short and " +"descriptive, such as `4 Weeks Vacation` or `Dental Plan`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:141 +msgid "" +":guilabel:`Proposed`: 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/add-new-applicants.rst:143 +msgid "" +":guilabel:`Other Benefits`: If any benefits are offered to the applicant, " +"enter them in the :guilabel:`Other Benefits` text field to the right of the " +":guilabel:`Proposed` field. The benefits should be short and descriptive, " +"such as `Unlimited Sick Time` or `Health Insurance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:148 +msgid "Job section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:150 +msgid "" +"The following fields are pre-populated when creating a new applicant, as " +"long as these fields are specified on the job position form. Editing the " +"fields is possible, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:153 +msgid "" +":guilabel:`Department`: select the department the job position falls under " +"from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:155 +msgid "" +":guilabel:`Company`: select the company the job position is for using the " +"drop-down menu. This field **only** appears when in a multi-company " +"database." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:159 +msgid "Sourcing section" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:161 +msgid "" +"This section houses the details regarding the way the applicant applied for " +"the job position. This information is necessary for :doc:`employee referrals" +" <../referrals>`, and allows for reporting on the channels with the highest " +"applicant generation." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:165 +msgid "" +":guilabel:`Source`: Using the drop-down menu, select where the applicant " +"learned about the job position. The following options come preconfigured in " +"Odoo: :guilabel:`Search engine`, :guilabel:`Lead Recall`, " +":guilabel:`Newsletter`, :guilabel:`Facebook`, :guilabel:`X`, " +":guilabel:`LinkedIn`, :guilabel:`Monster`, :guilabel:`Glassdoor`, and " +":guilabel:`Craigslist`. To add a new :guilabel:`Source`, type in the source," +" then click :guilabel:`Create \"(new source)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:170 +msgid "" +":guilabel:`Medium`: Using the drop-down menu, specify how the job listing " +"was found. The preconfigured options are: :guilabel:`Banner`, " +":guilabel:`Direct`, :guilabel:`Email`, :guilabel:`Facebook`, " +":guilabel:`Google Adwords`, :guilabel:`LinkedIn`, :guilabel:`Phone`, " +":guilabel:`SMS`, :guilabel:`Television`, :guilabel:`Website`, :guilabel:`X` " +"(formerly \"Twitter\"), or :guilabel:`[Push Notifications] (website name)`. " +"To add a new :guilabel:`Medium`, type in the medium, then click " +":guilabel:`Create \"(new medium)\"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:176 +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 field to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:-1 +msgid "All the fields of the Details tab for a new applicant form entered." +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:184 +msgid "Skills tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/add-new-applicants.rst:186 +msgid "" +"Skills can be added to the applicant's card. For details on adding skills, " +"refer to the :ref:`Create new employees ` document." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:3 +msgid "Applicant analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:5 +msgid "" +"The *Applicant Analysis* report allows recruiting departments to see which " +"job positions have the most applicants, which have the most referrals, and " +"how long it takes for applicants to move through the pipeline." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:9 +msgid "" +"Knowing how many applicants each specific job position has, along with " +"statistics about how many are hired and refused, can provide valuable " +"insights. This information can assist the recruiting team to pivot their " +"strategies to acquire the most desirable candidates." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:14 +msgid "Applicant analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:16 +msgid "" +"Start by navigating to :menuselection:`Recruitment app --> Reporting --> " +"Applicant Analysis`. This presents a line chart of all applicants for the " +"last year." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:19 +msgid "" +"Three separate color-coded metrics are presented: :guilabel:`In Progress`, " +":guilabel:`Hired`, and :guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:22 +msgid "" +"Hover the cursor over a month of the chart, and a pop-up window appears, " +"displaying the specific numbers for that month." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "The default Applicant Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:29 +#: ../../content/applications/hr/recruitment/team_performance.rst:30 +msgid "Pivot table view" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:31 +msgid "" +"For a more detailed view of the information in the :guilabel:`Applicant " +"Analysis` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` icon " +"in the top-right corner. This displays all the information in a pivot table." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:35 +msgid "" +"In this view, the job positions are displayed in the rows, and the columns " +"display the total numbers of applicants, including how many of those " +"applicants were hired or refused, and who is still in the recruitment " +"process. The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:39 +msgid "" +"In this example, there are 18 total applicants. Out of that, six have been " +"hired, two have been refused, and ten are still in the recruitment pipeline." +" The :guilabel:`Experienced Developer` position has six total applicants, " +"three of which were hired, one refused, and two still in progress." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The detailed pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:48 +msgid "Use case: applicants with referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:50 +msgid "" +"To get a better understanding of how effective the company's :doc:`referral " +"program <../referrals>` is, the :guilabel:`Applicant Analysis` report can be" +" modified to show how many applicants were referred by current employees." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:54 +msgid "" +"From the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view of the " +":guilabel:`Applicant Analysis` report, first click the :guilabel:`Measures` " +"button to reveal a drop-down menu of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:57 +msgid "" +"Click both :guilabel:`Has Referrer` and :guilabel:`Count`, to activate those" +" two measures. Then, click :guilabel:`Applicant`, :guilabel:`Hired`, " +":guilabel:`In Progress` and :guilabel:`Refused` to deactivate those default " +"measures." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:61 +msgid "" +"Now, the column displays the number of applicants that came from a referral " +"in the :guilabel:`Has Referrer` column, and the total number of applicants " +"in the :guilabel:`Count` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying the number of referrals and the " +"total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:67 +msgid "" +"In this example, the :guilabel:`Experienced Developer` and " +":guilabel:`Interior Designer` job positions both have applicants from " +"referrals, while the rest do not have any referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:71 +msgid "Hired through referrals" +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:73 +msgid "" +"It is possible to modify this report even further to see how many referred " +"applicants end up being hired." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:76 +msgid "" +"To view this data, click on a :icon:`fa-plus-square` :guilabel:`[job " +"position]` row, which reveals a drop-down menu. Then, click " +":guilabel:`State` to show the various states applicants are currently in." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:81 +msgid "" +"Only states that have applicants in them are shown for each job position. If" +" a state does **not** have any applicants, it does not appear in the list." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:84 +msgid "" +"To expand the other rows, and display the various states, click on the " +":icon:`fa-plus-square` :guilabel:`[job position]` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:-1 +msgid "" +"The detailed pivot table view displaying applicants hired through referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/applicant_analysis.rst:90 +msgid "" +"Both the :guilabel:`Experienced Developer` and :guilabel:`Interior Designer`" +" roles yielded one referral hire each, confirming that developers and " +"designers generate the highest-success referrals." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:5 +msgid "" +"In Odoo's **Recruitment** application, all job positions are shown on the " +"default dashboard in the **Recruitment** app, which includes both active and" +" inactive positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:8 +msgid "" +"Each job position is shown in an individual Kanban card. If the job position" +" is active, and candidates can apply, a :guilabel:`PUBLISHED` banner appears" +" in the top-right corner of the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:11 +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 app showing all job positions." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:19 +msgid "Create a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:21 +msgid "" +"To create a new job position from the main dashboard in the **Recruitment** " +"app, click the :guilabel:`New` button in the top-left corner, and a " +":guilabel:`Create a Job Position` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:25 +msgid "" +"First, enter the name of the :guilabel:`Job Position` (such as `Sales " +"Manager`, `Mechanical Engineer`, etc.) in the field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:28 +msgid "" +"Next, enter an :guilabel:`Application email` by typing in the first half of " +"the email address in the first field, then select the second half of the " +"email using the drop-down menu in the second field. Applicants can send a " +"resumé to this specific email address, and Odoo creates an application for " +"them automatically." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:33 +msgid "" +"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:39 +msgid "" +"Once the job position has been created, it appears as a card in the Kanban " +"view on the main **Recruitment** app dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:45 +msgid "Edit a new job position" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:47 +msgid "" +"After the job position is created, it is time to enter the details for the " +"position. Click on the :icon:`fa-ellipsis-v` :guilabel:`(Dropdown menu)` " +"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:55 +msgid "" +"The top-right corner of the card has a toggle to publish the job position to" +" the website. If the job position is published, a green " +":guilabel:`Published` toggle is visible. If the job position is *not* " +"published a gray :guilabel:`Not Published` toggle appears. Click the toggle " +"to publish or unpublish the job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:61 +msgid "Recruitment tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:63 +msgid "" +"All the basic information about the job position is listed under the " +":guilabel:`Recruitment` tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:65 +msgid "" +"None of the fields are required, but it is important to configure and " +"populate the :guilabel:`Department`, :guilabel:`Job Location`, " +":guilabel:`Employment Type` fields, and the :guilabel:`Job Summary` tab, as " +"they are all visible to prospective applicants on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:70 +msgid "" +"Some fields listed below may not appear depending on the database " +"configuration and other installed applications." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:73 +msgid "The fields can be filled out as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:75 +msgid "" +":guilabel:`Department`: Select the relevant department for the job position." +" This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:77 +msgid "" +":guilabel:`Job Location`: Select the physical address for the job. If the " +"job position is remote, leave this field blank. This is visible on the " +"website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:79 +msgid "" +":guilabel:`Industry`: Select the relevant industry the job position falls " +"under. This field corresponds to the industries on job boards. Odoo comes " +"with 86 preconfigured industries. It is *not* recommended to add a new " +"industry, as it may hide the job position during some searched on the " +"various job boards." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:83 +msgid "" +":guilabel:`Email Alias`: Enter an email address to which applicants can send" +" a resumé. Once emailed, Odoo automatically creates an application for them." +" If an email was entered when creating the job position, this field is " +"populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:86 +msgid "" +":guilabel:`Employment Type`: select what type of position the job is, using " +"the drop-down menu. The default options are :guilabel:`Permanent`, " +":guilabel:`Temporary`, :guilabel:`Seasonal`, :guilabel:`Full-Time`, " +":guilabel:`Intern`, :guilabel:`Student`, :guilabel:`Apprenticeship`, " +":guilabel:`Thesis`, :guilabel:`Statutory`, and :guilabel:`Employee`. " +"Depending on the installed localization, other options may be available. " +"This is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:91 +msgid "" +":guilabel:`Working Schedule`: Select the working schedule for the job " +"position. Odoo provides one working schedule by default, :guilabel:`Standard" +" 40 hours/week`, but all working schedules in the database are available." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:94 +msgid "" +":guilabel:`Salary Range`: Enter both the minimum and maximum salaries " +"offered for the position in the two fields. Then, set the last field to the " +"time-frame for the salary range. The default options are :guilabel:`Hour`, " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Bi-Week`, :guilabel:`Month`, " +"and :guilabel:`Year`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:98 +msgid "" +":guilabel:`Expected Skills`: Select all the desired skills for the job " +"position, using the drop-down menu. The skills presented are " +":ref:`configured in the Employees app `." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:101 +msgid "" +":guilabel:`Company`: Select the company the job is for. This field only " +"appears if using a multi-company database." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:103 +msgid "" +":guilabel:`Mission Dates`: Using the calendar selector, set the start date " +"for the job position. If the job is temporary and has a specific end date, " +"set the end date in the second field." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:105 +msgid "" +":guilabel:`Target`: Enter the number of employees to be hired for this " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:106 +msgid ":guilabel:`Website`: Select the website the job is published on." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:107 +msgid "" +":guilabel:`Recruiter`: Select the person responsible for recruiting this " +"role." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:108 +msgid "" +":guilabel:`Interviewers`: Select who should perform the interviews. Multiple" +" people can be selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:110 +msgid "" +":guilabel:`Interview Form`: select an :ref:`Interview form " +"` that applicants fill out prior to their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:112 +msgid "" +":guilabel:`Contract Template`: Select a contract template to be used when " +"offering the job to a candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The job information details in the Recruitment tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:119 +msgid "Job summary tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:121 +msgid "" +"Enter the job description in the :guilabel:`Job Summary` tab. This " +"description is visible on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:-1 +msgid "The summary of the position in the Job Summary tab." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:128 +msgid "Application info tab" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:130 +msgid "" +"The :guilabel:`Process Details` section of the :guilabel:`Application Info` " +"tab 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:134 +msgid "" +"The following fields are populated by default, but can be modified to suit " +"the recruitment timeline of the business:" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:137 +msgid "" +":guilabel:`Time to Answer`: Enter the number of days before the applicant is" +" contacted. :guilabel:`2 open days` populates this field by default." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:139 +msgid "" +":guilabel:`Process`: Enter the various stages the candidate goes through " +"during the recruitment process. By default, two process steps are visible: " +":guilabel:`1 Phone Call` and :guilabel:`1 Onsite Interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:142 +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. " +"The default is :guilabel:`4 Days after Interview`." +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:149 +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:156 +msgid "Create interview form" +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:158 +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:162 +msgid "" +"Before creating an interview form, ensure the proper settings are enabled. " +"Navigate to :menuselection:`Recruitment app --> Configuration --> Settings`," +" and under the :guilabel:`Recruitment Process` section, ensure the " +":guilabel:`Send Interview Survey` option is enabled." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:167 +msgid "" +"Since there are no preconfigured forms in Odoo, all interview forms must be " +"created. To create an interview form, start from the :guilabel:`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:`Search More...`, 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:-1 +msgid "The blank interview form pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/new_job.rst:178 +msgid "" +"The option :guilabel:`Search More...` 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:182 +msgid "" +"Proceed to fill out the interview form pop-up window as a typical survey. " +"For specific directions on how to create a survey, refer to the :doc:`survey" +" essentials <../../marketing/surveys/create>` document, which provides step-" +"by-step instructions on how to create and configure a survey." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:3 +msgid "Offer job positions" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:5 +msgid "" +"After an applicant has successfully passed the various interview stages, the" +" recruitment team is ready to send an offer for employment. The first step " +"when offering a job position is to send the applicant a contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:10 +msgid "" +"Refer to the :doc:`recruitment <../recruitment>` documentation for details " +"on the various stages of the recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:14 +msgid "Contract proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:16 +msgid "" +"When an offer is ready to be sent, first open the applicant's card by " +"navigating to the :menuselection:`Recruitment app`, and clicking on the " +"desired job position card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:19 +msgid "" +"From the resulting :guilabel:`Job Positions` Kanban view, the corresponding " +"applicant card can be dragged-and-dropped to the :guilabel:`Contract " +"Proposal` stage. Or, click into the desired applicant's card, and click the " +":guilabel:`Contract Proposal` stage, located in the status bar in the top-" +"right of the applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:24 +msgid "" +"The next step is to send an offer to the applicant. Start by selecting the " +"desired applicant's card to open their applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:27 +msgid "" +"On the applicant's form, click the :guilabel:`Generate Offer` button to load" +" the :guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:31 +msgid "" +"If the applicant does not have an email address listed on their applicant " +"card, an :guilabel:`Invalid Operation` pop-up window warning appears, " +"stating: :guilabel:`Offer link can not be send. The applicant needs to have " +"a name and email.`" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:35 +msgid "" +"Click :guilabel:`Close`, then enter an email on the applicant's card. Once " +"an email is entered, click the :guilabel:`Generate Offer` button, and the " +":guilabel:`Offer for (applicant's email)` page loads." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:39 +msgid "" +"Most fields are pre-populated with information from the job position. If any" +" necessary fields are blank, or if any information needs to be updated, " +"enter, or update, the relevant information in the corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:44 +msgid "" +"Depending on the localization setting for the company, and which " +"applications are installed, some fields may not appear on the " +":guilabel:`Offer for (applicant's email)` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:47 +msgid "" +"For example, if the **Fleet** application is **not** installed, any fields " +"related to vehicles do **not** appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:51 +msgid "Universal fields" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:53 +msgid "" +"The following fields appear in the :guilabel:`Offer for (applicant's email)`" +" page, regardless of the localization." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:56 +msgid "" +":guilabel:`Title`: The name for the contract appears in a default `Offer for" +" (applicant's email)` format." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:58 +msgid "" +":guilabel:`Contract Template`: The template currently being used to populate" +" the :guilabel:`Offer for (applicant's email)` page. Use the drop-down menu " +"to select a different :guilabel:`Contract Template`, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:63 +msgid "" +"To modify the template, hover over the current template name, and click the " +":icon:`fa-arrow-right` :guilabel:`(Internal link)` icon that appears to the " +"right of the field. Make any desired changes, then click :guilabel:`Save & " +"Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:67 +msgid "" +":guilabel:`Employer Budget`: The salary being offered to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:68 +msgid "" +":guilabel:`Job Title`: The selected :guilabel:`Employee Job` populates this " +"field, by default. The title can be modified to suit the specific " +"applicant's position and provide more details." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:72 +msgid "" +"An applicant is offered a marketing manager job at a shoe company, " +"specifically for the children's line." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:75 +msgid "" +"The :guilabel:`Employee Job` selected from the drop-down menu is `Marketing " +"Manager`, and the :guilabel:`Job Title` is modified for their specific " +"responsibilities, `Marketing Manager: Children's Shoes`." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:79 +msgid "" +":guilabel:`Employee Job`: The name of the :guilabel:`Job Title` being " +"offered to the applicant. The selections available in the drop-down menu " +"correspond to the job position configured on the main **Recruitment** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:83 +msgid ":guilabel:`Department`: The department the job position falls under." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:84 +msgid "" +":guilabel:`Contract Start Date`: The date the proposed contract takes " +"effect. The default date is the current date. To modify the date, click on " +"the displayed date to reveal a calendar popover window. Navigate to the " +"desired month, then click the day to select the date." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:87 +msgid "" +":guilabel:`Offer Create Date`: The day the offer is created, By default, the" +" current date populates this field and *cannot* be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:89 +msgid "" +":guilabel:`Offer Validity Date`: The last day the offer is valid. After this" +" date the contract cannot be signed." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:91 +msgid "" +":guilabel:`Link`: The link to the contract being sent to the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:92 +msgid "" +":guilabel:`Validity Days Count`: The number of days the contract is valid. " +"The default expiration date is `30` days. Modify the expiration date, if " +"desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:94 +msgid "" +":guilabel:`Applicant`: The name of the applicant appears in this field, and " +"cannot be modified." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:97 +msgid "Send offer" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:99 +msgid "" +"Once all desired modifications have been made to the :guilabel:`Offer for " +"(applicant's email)` page, click the :guilabel:`Send By Email` button to " +"reveal an email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:102 +msgid "" +"The default `Recruitment: Your Salary Package` email template is used, and " +"the :guilabel:`To`, :guilabel:`Subject`, and email body are pre-populated " +"based on the email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:105 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`(paperclip)` 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 at the bottom of the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:109 +msgid "" +"Once the email is ready to send, click :guilabel:`Send`. The email pop-up " +"window closes, and an :icon:`fa-handshake-o` :guilabel:`Offers` smart button" +" appears at the top of the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:113 +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, and " +"they can actually sign the offer. The applicant does **not** need any " +"software installed to sign the offer." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Send an email to the applicant with a link to the offered salary." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:121 +msgid "Configure your package" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:123 +msgid "" +"If applicable, the applicant can modify their salary package. This option is" +" not available for all localizations. Depending on where the company is " +"located, this option may not be available." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:126 +msgid "" +"The email template includes a :guilabel:`Configure your package` button. " +"This link takes the applicant to a webpage, where they can modify the " +"proposed salary package, and enter their personal information." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:130 +msgid "" +"Once the applicant is hired, the personal information entered on the webpage" +" is imported to their employee record, when created." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:133 +msgid "" +"Once all the information is completed, the applicant can then accept the " +"offer by clicking the :guilabel:`Review Contract & Sign` button to accept " +"the contract, and sign it using the **Sign** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:138 +msgid "Management signatures" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:140 +msgid "" +"Once the applicant has signed the contract, the next step is for the person " +"responsible within the company (the :guilabel:`HR Responsible`) must then " +"sign the contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:143 +msgid "" +"The person responsible for signing the contract receives an activity alert " +"that their signature is requested of them in the **Sign** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:149 +msgid "Contract signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:151 +msgid "" +"Once all parties have fully signed the contract, the applicant is " +"automatically moved to the :guilabel:`Contract Signed` stage, and a green " +":guilabel:`HIRED` banner appears in the top-right of both the applicant's " +"card and form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:-1 +msgid "Hired banner in the top-right corner of applicant card." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:161 +msgid "Create employee" +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:163 +msgid "" +"Once the applicant has been hired, the next step is to create their employee" +" record. Click the :guilabel:`Create Employee` button in the top-left corner" +" of the hired applicant's form." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:166 +msgid "" +"An employee form appears, with information from the applicant's card, and " +"the employee contract." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:168 +msgid "" +"Fill out the rest of the employee form. For detailed information on the " +"fields, refer to the :doc:`../employees/new_employee` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/offer_job_positions.rst:171 +msgid "Once completed, the employee record is saved in the **Employees** app." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:3 +msgid "Recruitment flow" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:5 +msgid "" +"When a prospective employee applies for a job in Odoo, there is a " +"preconfigured process from the :ref:`initial inquiry ` to " +"the :ref:`creating of a new employee ` once hired." +" The following outlines the default recruitment process for Odoo's " +"**Recruitment** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:11 +msgid "" +"The following is based on Odoo's default recruitment pipeline. Be advised " +"that if :ref:`modifications are made ` to the " +"pipeline, the process differs." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:20 +msgid "" +"At the start of the process, all applicants appear in the :guilabel:`New` " +"stage on the :guilabel:`Applications` page, whether submitted online or if " +"the applicant is :doc:`manually entered by a recruiter `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:24 +msgid "" +"The :guilabel:`Candidate`, :guilabel:`Email`, and :guilabel:`Phone` number " +"on the applicant's card are filled as soon as it is created. By default, " +"these details are required for every job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:28 +msgid "" +"If the website application form is modified, different fields may be " +"populated, based on what information is required on the website." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:31 +msgid "" +"Anything typed in the *Short Introduction* section appears in the " +"applicant's chatter as an :guilabel:`Other Information` note from " +":guilabel:`OdooBot`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:37 +msgid "" +"If a resumé was attached to the online application, it appears in the " +":guilabel:`Files` section of the chatter, and is also stored in the " +"**Documents** application." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:40 +msgid "" +"To find the recruitment documents, navigate to the main " +":menuselection:`Documents app` dashboard, and click the " +":guilabel:`Recruitment` folder on the left-hand side. All recruitment " +"documents are stored within that folder." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:44 +msgid "" +"If the :ref:`CV Display ` option was enabled in the " +":ref:`Settings ` of the **Recruitment** app, the " +"resumé appears on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:48 +msgid "" +"Depending on the browser zoom level, or size of the browser screen, the " +"resumé may appear below the main applicant card information as a PDF link, " +"or on the right side as an image." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:52 +msgid "Send interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:54 +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/recruitment-flow.rst:57 +msgid "" +"The **Surveys** application is required to send interviews to an applicant, " +"so it **must** be installed." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:60 +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 more " +"information on creating and editing interviews, refer to the " +":doc:`../../hr/recruitment/new_job` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:66 +msgid "" +"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." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:71 +msgid "" +"To send an interview to an applicant, first click the applicant's card from " +"the :guilabel:`Applications` page, to view the detailed applicant " +"information. At the top-left of the applicant's card, click the " +":guilabel:`Send Interview` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:75 +msgid "" +"If the applicant's card has an email address on file, a :guilabel:`Send an " +"interview` pop-up window appears, with the :guilabel:`Recipients`, " +":guilabel:`Subject`, and email body populated." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:79 +msgid "" +"To send an email to an applicant, there **must** be an :guilabel:`Email` " +"address on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:82 +msgid "" +"If an email address is not entered on the applicant's card, when the " +":guilabel:`Send Interview` button is clicked, an :guilabel:`Edit: " +"(Applicant's Name)` pop-up window appears, *on top of* the :guilabel:`Send " +"an interview` pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:86 +msgid "" +"Enter the email address in the :guilabel:`Email` field, then click " +":guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:88 +msgid "" +"Once the applicant's information is saved, the :guilabel:`Edit: (Applicant's" +" Name)` pop-up window closes, and the :guilabel:`Send an interview` pop-up " +"window remains." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:91 +msgid "" +"Sometimes, preconfigured email templates in Odoo use dynamic placeholders, " +"which are automatically filled with specific data when the email is sent. " +"For example, if a placeholder for the applicant's name is used, it is " +"replaced with the actual name of the applicant in the email. For more " +"detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:97 +msgid "" +"Add the email addresses of any additional recipients for the survey in the " +":guilabel:`Additional emails` field, if more people should receive the " +"email. If an email address is in the database as a contact, add that contact" +" in the :guilabel:`Recipients` field. 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 address in the :guilabel:`Additional emails` " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:103 +msgid "" +"If any attachments need to be added, click the :icon:`fa-paperclip` " +":guilabel:`Attachments` button, and a file explorer window appears. Navigate" +" to the desired file, and click :guilabel:`Open` to attach it to the email. " +"The attachment loads, and is listed above the :icon:`fa-paperclip` " +":guilabel:`Attachments` button." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:108 +msgid "" +"If the emailed interview must be completed by a specific date, enter that " +"date in the :guilabel:`Answer deadline` field, located in the lower-right " +"area of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:111 +msgid "" +"To do so, click the empty field next to :guilabel:`Answer deadline`, and a " +"calendar selector appears. Use the :icon:`fa-chevron-left` " +":guilabel:`(left)` and :icon:`fa-chevron-right` :guilabel:`(right)` arrows, " +"on either side of the month, to navigate to the desired month. Then, click " +"on the desired day to select the date. Next, select the time the interview " +"is due, in the two fields at the bottom of the calendar selector." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:117 +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/recruitment-flow.rst:121 +msgid "" +"To send the email with the interview link to the applicant, click " +":guilabel:`Send` at the bottom of the email pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:131 +msgid "Initial qualification" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:133 +msgid "" +"If an applicant seems to be a good potential candidate, they are moved to " +"the :guilabel:`Initial Qualification` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:136 +msgid "" +"This stage exists to sort candidates that have potential, from those that do" +" not meet the requirements. No automatic actions, such as emails, are set " +"for this stage. This stage informs the recruitment team to potentially set " +"up a phone call or an interview with the candidate." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:141 +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 of the" +" :guilabel:`Applications` page to the desired stage, or the stage can be " +"modified on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:145 +msgid "" +"To change the stage on the applicant's card, first click the desired " +"applicant's card from the :guilabel:`Applications` page. The current stage " +"for the card is highlighted at the top on a status bar, above the card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:149 +msgid "" +"Click the desired stage for the card, and the stage changes. A log note " +"indicating the stage change appears in the chatter, as well." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:0 +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/recruitment-flow.rst:159 +msgid "First interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:161 +msgid "" +"After an applicant has passed the :guilabel:`Initial Qualification` stage, " +"they can be manually moved to the :guilabel:`First Interview` stage on the " +":guilabel:`Applications` page, while in Kanban view." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:165 +msgid "" +"To move the applicant to the next stage, drag-and-drop the applicant's card " +"to the :guilabel:`First Interview` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:168 +msgid "" +"Alternatively, open the desired applicant's card from the " +":guilabel:`Applications` page, and click the :guilabel:`First Interview` " +"stage on the status bar at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:173 +msgid "" +"The :guilabel:`First Interview` stage can be modified, so when the " +"applicant's card moves to the :guilabel:`First Interview` stage, an email " +"can be automatically sent to the applicant, stating an interview is " +"requested. In this preconfigured email template, a link to the recruiting " +"team's calendar appears, allowing the applicant to schedule their interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:178 +msgid "" +":ref:`Edit ` the :guilabel:`First Interview` stage, " +"and select the :guilabel:`Recruitment: Schedule Interview` option in the " +":guilabel:`Email Template` field, to automate this action." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:185 +msgid "Second interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:187 +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 from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Second Interview` " +"stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:193 +msgid "" +"When the applicant's card moves to the :guilabel:`Second Interview` stage, " +"there are no automatic activities or emails configured for this stage, by " +"default. The recruiter can now :ref:`schedule a second interview " +"` with the applicant," +" following the same process as the first interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:201 +msgid "Contract Proposal" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:203 +msgid "" +"After the applicant has completed the various interview processes, the next " +"step is to :doc:`send the job offer `." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:206 +msgid "" +"Once the offer has been sent, drag-and-drop the applicant's card to the " +":guilabel:`Contract Proposal` stage from the Kanban view of the " +":guilabel:`Applications` page, or click on the :guilabel:`Contract Proposal`" +" stage at the top of the individual applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:211 +msgid "Contract Signed" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:213 +msgid "" +"Once the contract has been signed, and the applicant has been hired, the " +"applicant's card moves to the :guilabel:`Contract Signed` stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:216 +msgid "" +"Drag-and-drop the applicant's card to the :guilabel:`Contract Signed` stage " +"from the Kanban view of the :guilabel:`Applications` page, or click the " +":icon:`fa-ellipsis-h` :guilabel:`(ellipsis)` icon at the top of the " +"individual applicant's card, then click :guilabel:`Contract Signed` on the " +"status bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:222 +msgid "Refuse applicant" +msgstr "" + +#: ../../content/applications/hr/recruitment/recruitment-flow.rst:224 +msgid "" +"At any point in the recruitment process, a candidate can be :doc:`refused " +"`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:3 +msgid "Refuse applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:5 +msgid "" +"At any point in the recruitment process, an applicant can be refused for a " +"job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:7 +msgid "" +"To refuse an applicant, start by navigating to the applicant's card in the " +"**Recruitment** app. This is done in one of two ways:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:10 +msgid "" +"Navigate to :menuselection:`Recruitment app --> Applications --> All " +"Applications`. In the :guilabel:`Applications` list, click anywhere on the " +"desired applicant's line to open that specific applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:13 +msgid "" +"Navigate to the main *Job Positions* dashboard by navigating to " +":menuselection:`Recruitment app --> Applications --> By Job Position`. Next," +" click on the desired job position card, then click on the individual " +"applicant card from the :guilabel:`Applications` page." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:17 +msgid "" +"At the top of the applicant's card, there are several buttons. Click the one" +" labeled :guilabel:`Refuse`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:23 +msgid "Refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:25 +msgid "" +"*Refuse reasons* allow recruiters to document why an applicant was not a " +"good fit, and send specific refusal reason email templates to the applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:28 +msgid "" +"Clicking :guilabel:`Refuse` on an applicant's form makes the " +":guilabel:`Refuse Reason` pop-up window appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:31 +msgid "" +"The default refuse reasons in Odoo, and their corresponding email templates," +" are:" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:37 +msgid "Email Template" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:38 +msgid "Refusal Reason" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:39 +msgid ":guilabel:`Recruitment: Refuse`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Does not fit the job requirements`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Job already fulfilled`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Duplicate`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Spam`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:44 +msgid ":guilabel:`Recruitment: Not interested anymore`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: job fit`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:0 +msgid ":guilabel:`Refused by applicant: salary`" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:48 +msgid "" +"Additional refusal reasons :ref:`can be created, and existing ones can be " +"modified (or deleted) `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:51 +msgid "" +"Select a refusal reason to :ref:`send a refusal email `." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:56 +msgid "Create or modify refuse reasons" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:58 +msgid "" +"To view and configure refuse reasons, navigate to " +":menuselection:`Recruitment app --> Configuration --> Refuse Reasons`. Doing" +" so reveals the :guilabel:`Refuse Reasons` page, where all the existing " +"refusal reasons are listed." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:62 +msgid "" +"To create a new refuse reason from the :guilabel:`Refuse Reasons` page, " +"click the :guilabel:`New` button in the top-left corner. A blank line " +"appears at the bottom of the list, with an empty field present in the " +":guilabel:`Description` column." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:66 +msgid "" +"Type in the new refuse reason in the field. It is recommended to enter a " +"reason that is short and concise, such as `Offer expired` or `Withdrew " +"application`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:69 +msgid "" +"Then, in the :guilabel:`Email Template` field, click on the field to reveal " +"a drop-down menu. Select an :guilabel:`Email Template` from the list to be " +"used when this refuse reason is selected." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:72 +msgid "" +"If a new :guilabel:`Email Template` is desired, type in the name for the new" +" template in the field. Then, click :guilabel:`Create and edit...`, and a " +":guilabel:`Create Email Template` form pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:76 +msgid "" +"In the :guilabel:`Create Email Template` pop-up window, enter a " +":guilabel:`Name` for the form, and an email :guilabel:`Subject` in the " +"corresponding fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:79 +msgid "" +"Enter the desired email content in the :guilabel:`Content` tab. Proceed to " +"make any other modifications to the template in the :guilabel:`Email " +"Configuration` and :guilabel:`Settings` tabs, then click :guilabel:`Save & " +"Close` to save the template. Upon clicking that, Odoo returns to the " +":guilabel:`Refuse Reasons` list." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:84 +msgid "" +"The new template appears in the new refuse reason :guilabel:`Email Template`" +" field." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:87 +msgid "" +"Pre-configured recruitment refusal email templates in Odoo use dynamic " +"placeholders, which are personalized placeholders that populate data from " +"the applicant's record in the email body." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:90 +msgid "" +"For example, if the applicant's name is a used in a dynamic placeholder, the" +" applicant's name appears anytime that dynamic placeholder appears on the " +"email template." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:93 +msgid "" +"For more detailed information on email templates, refer to the " +":doc:`../../general/companies/email_template` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:99 +msgid "Send refusal email" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:101 +msgid "" +"After clicking the :guilabel:`Refuse` button on an applicant form, a " +":ref:`Refuse Reason ` is then selected from the " +":guilabel:`Refuse Reason` pop-up window. Then, two fields appear below the " +"selected refusal reason: :guilabel:`Send Email` and :guilabel:`Email " +"Template`." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"The Refuse Reason pop-up window that appears when refusing an applicant." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:109 +msgid "" +"The applicant's email address automatically populates the :guilabel:`Send " +"Email` field; additional email recipients **cannot** be added." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:112 +msgid "" +"If an email should **not** be sent to the applicant, uncheck the " +":guilabel:`Send Email` checkbox." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:114 +msgid "" +"The email template associated with the refusal reason populates the " +":guilabel:`Email Template` field. If a different email template is desired, " +"select a different template from the :guilabel:`Email Template` drop-down " +"menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:118 +msgid "" +"To send the refusal email to the applicant, ensure the :guilabel:`Send " +"Email` checkbox is ticked, then click :guilabel:`Refuse` at the bottom of " +"the :guilabel:`Refuse Reason` pop-up window. The refusal email is sent to " +"the applicant, and a red :guilabel:`Refused` banner appears on the " +"applicant's card in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:-1 +msgid "" +"An applicant's card with the refused banner appearing in the top-right " +"corner in red." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:127 +msgid "View refused applicants" +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:129 +msgid "" +"After refusal, the applicant's card is no longer visible in the job " +"position's Kanban view. However, it is still possible to view applicants who" +" have been refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:132 +msgid "" +"To view only the refused applicants, go to :menuselection:`Recruitment app " +"--> Applications --> By Job Positions`, or :menuselection:`Recruitment app " +"--> Applications --> All Applications`. Both methods navigate to the " +":guilabel:`Applications` dashboard, the only difference is :guilabel:`By Job" +" Positions` displays applicants in a Kanban view, while :guilabel:`All " +"Applications` displays applicants in a list view." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:138 +msgid "" +"On the :guilabel:`Applications` page, click the :icon:`fa-caret-down` " +":guilabel:`(Toggle Search Panel)` button in the search bar, then click " +":guilabel:`Refused`, located under the :icon:`fa-funnel` :guilabel:`Filters`" +" section." +msgstr "" + +#: ../../content/applications/hr/recruitment/refuse_applicant.rst:142 +msgid "" +"All applicants that have been refused for the job position appear on the " +":guilabel:`Applications` page for that position, organized by the stage they" +" were in when they were refused." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:3 +msgid "Schedule interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:5 +msgid "" +"An in-person, virtual, or phone interview can be scheduled in one of two " +"ways through the **Recruitment** app, either by the :ref:`recruitment team " +"`, or by the " +":ref:`applicant `." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:10 +msgid "" +"With one drag-and-drop, Odoo emails the candidate with a self-service link, " +"the candidate books the time slot, and sends the meeting to everyone's " +"calendar. No more back-and-forth emails or calls." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:16 +msgid "Recruitment team scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:18 +msgid "" +"When an applicant reaches the interview stage, the recruitment team should " +"schedule the interview, by first coordinating a suitable date and time with " +"the applicant and interviewers." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:21 +msgid "" +"To schedule the interview, navigate to the applicant's card, by first going " +"to the :menuselection:`Recruitment app`, and clicking the relevant job card." +" This opens the :guilabel:`Applications` page for that job position. Then, " +"click the desired applicant's card to view their detailed applicant form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:26 +msgid "" +"To schedule an phone, virtual, or in-person interview, click the :icon:`fa-" +"calendar` :guilabel:`No Meeting` smart button at the top of the applicant's " +"record." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:30 +msgid "" +"The :guilabel:`Meetings` smart button displays :icon:`fa-calendar` " +":guilabel:`No Meeting` if no meetings are currently scheduled. For " +"applicants who are new to the :guilabel:`First Interview` stage, this is the" +" default." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:34 +msgid "" +"If there is one meeting already scheduled, the smart button displays " +":guilabel:`1 Meeting`, with the date of the upcoming meeting beneath it. If " +"more than one meeting is scheduled, the button displays :guilabel:`Next " +"Meeting`, with the date of the first upcoming meeting beneath it." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:38 +msgid "" +"Clicking the :guilabel:`Meetings` smart button loads a calendar, showing the" +" scheduled meetings and events for the currently signed-in user, as well as " +"the employees who are listed under the :guilabel:`Attendees` section, " +"located to the right of the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:42 +msgid "" +"To change the currently loaded meetings and events being displayed, uncheck " +"an attendee whose calendar events are to be hidden. Only the checked " +"attendees are visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar view, highlighting how to change the displayed meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:48 +msgid "" +"To add a meeting to the calendar when in the *Day* or *Week* view, click on " +"the start time of the meeting and drag down to the end time. Doing so " +"selects the date, time, and the length of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:52 +msgid "" +"A meeting can also be added in this view by clicking on the desired day " +"*and* time slot." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:54 +msgid "" +"Both methods cause a :ref:`New Event ` pop-up window to appear." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:60 +msgid "New event pop-up window" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:62 +msgid "" +"Clicking a grid, corresponding with the time and date, opens the " +":guilabel:`New Event` pop-up window to schedule a meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:65 +msgid "" +"Enter the information on the form. The only required fields to enter are a " +"title for the meeting, along with the :guilabel:`Start` (and end date/time) " +"fields." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:68 +msgid "" +"Once the card details are entered, click :guilabel:`Save & Close` to save " +"the changes and create the interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:71 +msgid "" +"After entering in a required name for the meeting, the fields available to " +"modify on the :guilabel:`New Event` card are as follows:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:74 +msgid "" +":guilabel:`Meeting Title`: Enter the subject for the meeting. This should " +"clearly indicate the purpose of the meeting. The default subject is the " +":guilabel:`Candidate` name entered on the applicant's card." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:77 +msgid "" +":guilabel:`Start`: Configure the start and end date and times for the " +"meeting. Clicking either of these fields opens a calendar pop-up window. " +"Click on the desired date to select it, and then enter the time in the " +"corresponding field. Click :icon:`fa-check` :guilabel:`Apply` to close the " +"window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:81 +msgid "" +":guilabel:`All Day`: Tick the box to schedule an all-day interview. If this " +"box is ticked, the :guilabel:`Start` field changes to :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:83 +msgid "" +":guilabel:`Attendees`: Select the people who should attend the meeting. The " +"default attendees are the prospective candidate, and the assigned recruiter " +"for the job position. Add as many other people as desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:86 +msgid "" +":guilabel:`Videocall URL`: If the meeting is virtual, or if there is a " +"virtual option available, click :icon:`fa-plus` :guilabel:`Odoo meeting`, " +"and a URL is automatically created for the meeting, which populates the " +"field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:89 +msgid "" +":guilabel:`Description`: Enter a brief description in this field. There is " +"an option to enter formatted text, such as numbered lists, headings, tables," +" links, photos, and more. Use the powerbox feature, by typing a `/` to " +"reveal a list of options." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:93 +msgid "" +"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/schedule_interviews.rst:98 +msgid "More options" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:100 +msgid "" +"To add additional information to the meeting, click the :guilabel:`More " +"Options` button in the lower-right corner of the :ref:`New Event " +"` pop-up window. Enter any of " +"the following additional fields:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:104 +msgid "" +":guilabel:`Duration`: this field auto populates based on the " +":guilabel:`Start` (and end) date and time. If the meeting time is adjusted, " +"this field automatically adjusts to the correct duration length. The default" +" length of a meeting is one hour." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:107 +msgid "" +":guilabel:`Recurrent`: if the meeting should repeat at a selected interval " +"(not typical for a first interview), tick the checkbox next to " +":guilabel:`Recurrent`. Several additional fields appear when this is " +"enabled:" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:111 +msgid "" +":guilabel:`Timezone`: using the drop-down menu, select the " +":guilabel:`Timezone` for the recurrent meetings." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:113 +msgid "" +":guilabel:`Repeat`: choose :guilabel:`Daily`, :guilabel:`Weekly`, " +":guilabel:`Monthly`, :guilabel:`Yearly`, or :guilabel:`Custom` recurring " +"meetings. If :guilabel:`Custom` is selected, a :guilabel:`Repeat Every` " +"field appears beneath it, along with another time frequency parameter " +"(:guilabel:`Days`, :guilabel:`Weeks`, :guilabel:`Months`, or " +":guilabel:`Years`). Enter a number in the blank field, then select the time " +"period using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:118 +msgid "" +":guilabel:`Repeat on`: enabled when the :guilabel:`Weekly` option is " +"selected in the :guilabel:`Repeat` field. Choose the day the weekly meeting " +"falls on." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:120 +msgid "" +":guilabel:`Day of Month`: configure the two drop-down menu options to select" +" a specific day of the month, irrespective of the date (e.g. the first " +"Tuesday of every month). To set a specific calendar date, choose " +":guilabel:`Date of Month` and enter the calendar date in the field (e.g. " +"`15` to set the meeting to occur on the fifteenth of every month)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:124 +msgid "" +":guilabel:`Until`: using the drop-down menu, select when the meetings stop " +"repeating. The available options are :guilabel:`Number of repetitions`, " +":guilabel:`End date`, and :guilabel:`Forever`. If :guilabel:`Number of " +"repetitions` is selected, enter the number of total meetings to occur in the" +" blank field to the right. If :guilabel:`End date` is selected, specify the " +"date using the calendar pop-up window, or type in a date in a MM/DD/YYYY " +"format. :guilabel:`Forever` schedules meetings indefinitely." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:131 +msgid ":guilabel:`Location`: enter the location for the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:132 +msgid "" +":guilabel:`Tags`: select any tags for the meeting using the drop-down menu, " +"or add a new tag by typing in the tag and clicking :guilabel:`Create " +"\"tag\"`. There is no limit to the number of tags that can be used." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:135 +msgid "" +":guilabel:`Privacy`: select if the organizer appears either " +":guilabel:`Available` or :guilabel:`Busy` for the duration of the meeting. " +"Next, select the visibility of this meeting, using the drop-down menu to the" +" right of the first selection. 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/schedule_interviews.rst:142 +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/schedule_interviews.rst:144 +msgid "" +":guilabel:`Reminders`: select a reminder from the drop-down menu. Default " +"options include :guilabel:`Notification`, :guilabel:`Email`, and " +":guilabel:`SMS Text Message`, each with a specific time period before the " +"event (hours, days, etc). The chosen reminder chosen alerts the meeting " +"participants of the meeting, via the selected option at the specified time. " +"Multiple reminders can be selected in this field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "A new meeting card with all the details populated, and ready to save." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:154 +msgid "Send meeting to attendees" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:156 +msgid "" +"Once changes have been entered on the :ref:`New Event " +"` pop-up window, and the meeting" +" details are correct, the meeting can be sent to the attendees, via email or" +" text message, from the expanded event form (what is seen when the " +":guilabel:`More Options` button is clicked on in the :guilabel:`New Event` " +"pop-up window)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:161 +msgid "" +"To send the meeting via email, click the :icon:`fa-envelope` " +":guilabel:`EMAIL` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:164 +msgid "" +"A :guilabel:`Contact Attendees` email configurator pop-up window appears. A " +"pre-formatted email, using the default :guilabel:`Calendar: Event Update` " +"email template, populates the email body field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:167 +msgid "" +"The applicant, followers of the job application, as well as the user who " +"created the meeting, are added to the :guilabel:`To` by default. Make any " +"desired changes to the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "Enter the information to send the event via email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:173 +msgid "" +"To send the meeting via text message, click the :icon:`fa-mobile` " +":guilabel:`SMS` button next to the :guilabel:`Attendees` field on the " +"expanded meeting form. A :guilabel:`Send SMS` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:177 +msgid "" +"At the top, a blue banner appears if any attendees do not have valid mobile " +"numbers, and lists how many records are invalid. If a contact does not have " +"a valid mobile number listed, click :guilabel:`Close`, and edit the " +"attendee's record, then redo these steps." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:181 +msgid "" +"When no warning message appears, type in the message to be sent to the " +"attendees in the :guilabel:`Message` field. To add any emojis to the " +"message, click the :icon:`oi-smile-add` :guilabel:`(smile add)` icon on the " +"right-side of the pop-up window." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:185 +msgid "" +"The number of characters, and amount of text messages required to send the " +"message (according to GSM7 criteria) appears beneath the :guilabel:`Message`" +" field. 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/schedule_interviews.rst:-1 +msgid "Send a text message to the attendees of the meeting." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:194 +#: ../../content/applications/hr/referrals/share_jobs.rst:94 +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:`../../essentials/in_app_purchase` documentation." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:201 +msgid "Applicant scheduled interviews" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:203 +msgid "" +"Coordinating interview times typically requires several email exchanges and " +"can slow the recruitment process. Enabling Odoo's self-service scheduling " +"removes that bottleneck: when an applicant is moved to an interview stage, " +"the system automatically sends a scheduling link, records the selected slot," +" and updates all relevant calendars." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:208 +msgid "" +"This automation is turned off by default. To activate it, assign the " +":guilabel:`Recruitment: Schedule Interview` email template to either the " +":guilabel:`First Interview` or :guilabel:`Second Interview` stage (see " +":ref:`recruitment/schedule_interviews/modify-stage`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:217 +msgid "" +":ref:`Modify ` either the :guilabel:`First " +"Interview` or :guilabel:`Second Interview` stage so the stage's " +":guilabel:`Email Template` field is set to :guilabel:`Recruitment: Schedule " +"interview`." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The Recruitment: Schedule Interview email template populating the Email " +"Template field." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:225 +#: ../../content/applications/hr/referrals/share_jobs.rst:54 +msgid "Send email" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:227 +msgid "" +"After configuring the :guilabel:`First Interview` or :guilabel:`Second " +"Interview` stages to :ref:`send emails " +"`, drag-and-drop the applicant" +" card into one of these stages to send the email." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:232 +msgid "Self-scheduled interview" +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:234 +msgid "" +"When the applicant received the email, they click the :guilabel:`Schedule my" +" interview` button at the bottom of the email. This navigates the applicant " +"to a private online scheduling page, which is **only** accessible through " +"the emailed link." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:238 +msgid "" +"This page displays the :guilabel:`MEETING DETAILS` on the right side of the " +"screen. This includes the format and length of the meeting. In this example." +" the interview is virtual (:icon:`fa-video-camera` :guilabel:`Online`) and " +"the duration is a half hour (:icon:`fa-clock-o` :guilabel:`30 minutes`)." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:243 +msgid "" +"Then the applicant clicks on an available day on the calendar, signified by " +"purple text. Once a day is selected, they click on one of the available " +"times to select that date and time." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "The calendar screen with dates and times to schedule an interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:250 +msgid "" +"Be sure to check the :guilabel:`Timezone` field, beneath the calendar, to " +"ensure it is set to the correct time zone. Changing the time zone may alter " +"the available times presented." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:253 +msgid "" +"Once the date and time are selected, the applicant is navigated to an " +":guilabel:`Add more details about you` page. This page asks the applicant to" +" enter their :guilabel:`Full name`, :guilabel:`Email`, and :guilabel:`Phone " +"number`. The contact information entered on this form is how the applicant " +"is contacted to remind them about the scheduled interview." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:258 +msgid "" +"When everything is entered on the :guilabel:`Add more details about you` " +"page, the applicant clicks the :guilabel:`Confirm Appointment` button, and " +"the interview is scheduled." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:-1 +msgid "" +"The confirmation page with all the details for the interview displayed." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:264 +msgid "" +"After confirming the interview, the applicant is taken to a confirmation " +"page, where all the details of the interview are displayed. The option to " +"add the meeting to the applicant's personal calendars is available, through " +"the :guilabel:`Add to iCal/Outlook` and :guilabel:`Add to Google Agenda` " +"buttons, beneath the interview details." +msgstr "" + +#: ../../content/applications/hr/recruitment/schedule_interviews.rst:269 +msgid "" +"The applicant is also able to cancel or reschedule the interview, if " +"necessary, with the :guilabel:`Cancel your appointment` link at the bottom " +"of the confirmation." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:3 +msgid "Source analysis reporting" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:5 +msgid "" +"Reporting is a critical tool used by recruiting departments to gain insights" +" into the entire recruitment process." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:8 +msgid "" +"Determining where applicants come from can provide information about which " +"sources have the best results. This information is determined by the *Source" +" Analysis* report. With this data, recruitment teams can better pivot their " +"recruiting strategies to gain better applicants, in both quantity and " +"quality." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:14 +#: ../../content/applications/hr/recruitment/team_performance.rst:12 +msgid "Open report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:16 +msgid "" +"To access the *Source Analysis* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Source Analysis`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:19 +msgid "" +"This presents the data for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant`, in a default :icon:`fa-area-chart` :guilabel:`(Graph)` view, " +"showing the amount of applicants by :guilabel:`Source`, and further " +"separated by stage (:guilabel:`In Progress` and :guilabel:`Hired`)" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:23 +msgid "" +"Hover the cursor over any column to view the specific numbers fort that " +"column." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The default bar chart of the source analysis information." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:29 +msgid "Source effectiveness report" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:31 +msgid "" +"To identify which sources (e.g., job boards, social media, employee " +"referrals, company website) produce the most hires, the pivot table view of " +"the :guilabel:`Source Analysis` report can be configured to display further " +"details." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:35 +msgid "" +"To view the :guilabel:`Source Analysis` report in a pivot table, click the " +":icon:`oi-view-pivot` :guilabel:`(Pivot)` icon in the top-right corner. The " +"data is presented in a pivot table, with rows populated by job positions, " +"and columns populated by stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:39 +msgid "" +"To expand this chart to show what specific sources the applicants came from," +" click the :icon:`fa-plus-square` :guilabel:`Total` box above the columns, " +"to reveal a drop-down menu, and click :guilabel:`Source`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:43 +msgid "" +"Each column is then grouped by the source, such as: :guilabel:`Search " +"engine`, :guilabel:`Facebook`, :guilabel:`LinkedIn`, etc. Each source " +"displays a separate count for :guilabel:`Applicant`, :guilabel:`Hired`, and " +":guilabel:`Refused`." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:47 +msgid "" +"This information, as presented, makes it difficult to view the specific " +"numbers for each source. Click the :icon:`fa-exchange` :guilabel:`(Flip " +"axis)` icon, to swap the information. After that, the rows represent the " +"source, and the columns represent the job positions, further divided by " +"stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The axes flipped in the source analysis report, in pivot table view." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:54 +msgid "" +"In this view, the total number of applicants, hired employees, and refused " +"applicants, are displayed for each source, as well as for each stage by job " +"position." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:58 +msgid "Medium" +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:60 +msgid "" +"Viewing the medium for the applicants can be beneficial to see which " +"specific medium is more successful." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:63 +msgid "" +"*Mediums* are the specific methods the applicant used to discover and then " +"apply for job positions, such as organic search, paid search, social media " +"ad, email, etc." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:66 +msgid "" +"To further group the results by medium, click into one of the :icon:`fa-" +"plus-square` :guilabel:`[Source]` rows. Click :guilabel:`Medium` in the " +"resulting drop-down menu. The row presents the specific mediums, relevant to" +" that specific source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:70 +msgid "" +"Once :guilabel:`Medium` is selected for one source, clicking into another " +"row automatically reveals the specific metrics for the mediums for that " +"source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:-1 +msgid "The sources rows, expanded to also show the medium for each source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:77 +msgid "" +"The only mediums that appear for a source, are mediums that have been set on" +" an applicant's form. If a medium has **not** been set for any applicants, " +"the medium does not appear in the drop-down rows beneath the source." +msgstr "" + +#: ../../content/applications/hr/recruitment/source_analysis.rst:81 +msgid "" +"For example, if no applicants applied with the medium *Google Adwords*, that" +" medium does **not** appear beneath the *Search engine* source row." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:3 +msgid "Team performance" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:5 +msgid "" +"The *Team Performance* report in the **Recruitment** app shows how many " +"applicants each recruiter is managing." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:8 +msgid "" +"This information is determined by the individuals populating the " +":ref:`Recruiter ` field on each applicant " +"form." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:14 +msgid "" +"To access the *Team Performance* report, navigate to " +":menuselection:`Recruitment app --> Reporting --> Team Performance`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:17 +msgid "" +"The number of :guilabel:`In Progress`, :guilabel:`Hired`, and " +":guilabel:`Refused` applicants for each recruiter is displayed in a default " +":icon:`fa-area-chart` :guilabel:`(Graph)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:20 +msgid "" +"The information shown is for the :icon:`fa-filter` :guilabel:`Last 365 Days " +"Applicant` default filter, as displayed in the search bar." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:23 +msgid "" +"Hover the cursor over any column to view a popover window, displaying the " +"specific details for that column." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The default bar chart of the team performance report." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:32 +msgid "" +"For a more detailed view of the information in the :guilabel:`Team " +"Performance` report, click the :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"icon in the top-right corner. This displays all the information in a pivot " +"table." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:36 +msgid "" +"In this view, the job positions populate the rows, while the columns " +"populate the number of applicants. The first column, :guilabel:`Applicant`, " +"is the total number of applicants across all stages for that job position. " +"The subsequent columns display the total applicants that have been " +":guilabel:`Hired`, :guilabel:`Refused`, and :guilabel:`In Progress` for each" +" job position." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:41 +msgid "The displayed information can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:43 +msgid "" +"In this example, there are 20 total applicants. Out of those 20, eight have " +"been hired, five have been refused, and seven are still in the recruitment " +"process." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:46 +msgid "" +"From the data presented, the :guilabel:`Experienced Developer` job position " +"is the most successful. This job position has one of the highest number of " +"total applicants (tied with the :guilabel:`Marketing and Community Manager` " +"position), as well as the most hires." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:50 +msgid "" +"This pivot table also shows that the :guilabel:`Quality Control Inspector` " +"position is the hardest to fill, as it has the fewest total applicants." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:57 +msgid "Use case: recruiter performance over time" +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:59 +msgid "" +"One way to modify this report is to show how recruiters are performing over " +"time. To show this information, begin with the :guilabel:`Team Performance` " +"report in the :icon:`oi-view-pivot` :guilabel:`(Pivot)` view." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:63 +msgid "" +"Next, click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search" +" bar, revealing a drop-down menu. Click :guilabel:`Add Custom Group` " +":icon:`fa-caret-down` at the bottom of the :icon:`oi-group` :guilabel:`Group" +" By` column, then click :guilabel:`Recruiter`. Click away from the drop-down" +" menu to close it. Now, each row on the table represents a recruiter." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "The pivot table now displaying the recruiters in the rows." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:71 +msgid "" +"To compare the team's performance over different time periods, click the " +":icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar. Click " +":guilabel:`Application Date` :icon:`fa-caret-down` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing various time periods to select." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:75 +msgid "" +"In this example, the desired data is the comparison between the team's " +"performance in the third quarter (June - August) and the second quarter " +"(April - July). To do so, click :guilabel:`Q3`. Once clicked, the current " +"year is also ticked. In this example, it is :guilabel:`2025`." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:79 +msgid "" +"After making this selection, a :icon:`fa-adjust` :guilabel:`Comparison` " +"column appears. Click :guilabel:`Start Date: Previous Period` to compare the" +" third quarter with the second quarter, for the various recruiters." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:-1 +msgid "A comparison table of recruiter totals of Q2 and Q3." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:86 +msgid "" +"From this report, some things can be extrapolated: the total number of " +"applicants, the number of hired applicants, the number of refused " +"applicants, and the number of applicants still in the recruitment pipeline " +"all increased." +msgstr "" + +#: ../../content/applications/hr/recruitment/team_performance.rst:90 +msgid "" +"Additionally, :guilabel:`Maggie Davidsons` had the highest increase in " +"number of hired applicants during the third quarter, while their number of " +"refused applicants went down." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:3 +msgid "Time in stage analysis" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:5 +msgid "" +"The *Time In Stage Analysis* report provides information on how long " +"applicants stay in each stage of the recruitment process. This is important," +" as every job position has specific :ref:`process details " +"` that state the length of time " +"applicants should expect to wait between specific stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:10 +msgid "" +"Knowing how long applicants remain in each stage can help highlight possible" +" bottlenecks. Analyzing this data allows the recruitment team to assess each" +" stage, identify any issues, and pivot their strategies to move applicants " +"through each stage, within the expected time interval." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:15 +msgid "Time in stage analysis report" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:17 +msgid "" +"To access the report, navigate to :menuselection:`Recruitment app --> " +"Reporting --> Time in Stage Analysis`. By default, the report displays data " +"from all job positions, with the stages populating the x-axis, and the " +"number of days populating the y-axis, in a :icon:`fa-line-chart` " +":guilabel:`(Line Chart)`." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:22 +msgid "" +"The default filter is :guilabel:`Last 365 Days Applicant`, showing " +"information for the last 365 days." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:25 +msgid "" +"Hover over a stage in the line chart to reveal a popover window listing all " +"the job positions within it, and the average number of days each job " +"position sits in each stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:28 +msgid "" +"For a more visually digestible view of the information in the " +":guilabel:`Time In Stage Analysis` report, click the :icon:`fa-bar-chart` " +":guilabel:`(Bar Chart)` icon in the upper-left corner. This displays all the" +" information in a bar chart." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:32 +msgid "" +"In this view, it is easier to visualize the differences between the job " +"positions, regarding how long applicants stay in each stage. From this view," +" recruiters can more easily determine which job positions have delays or " +"bottlenecks at certain stages." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The bar chart view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:41 +msgid "Use case: comparing times by month" +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:43 +msgid "" +"With the :guilabel:`Time In Stage Analysis` report, it is possible to see if" +" there are certain months where applicants take longer to be moved through " +"the pipeline. To view this data, switch to the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` view in the upper-right corner." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:47 +msgid "" +"This presents the data in a detailed pivot table, with the rows representing" +" the different job positions, and the columns representing the stages. The " +"average :guilabel:`Days in Stage` populates the various boxes." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:52 +msgid "" +"If a field is empty, it indicates no applicant has been in that stage. " +"Instead, all applicants moved from a previous stage without being placed in " +"the stage with an empty field." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table view of the Time In Stage Analysis report." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:59 +msgid "" +"Click :icon:`fa-minus-square-o` :guilabel:`Total` above the job position " +"rows to collapse the information. Next, click :icon:`fa-plus-square` " +":guilabel:`Total` again, revealing a drop-down menu. Click :guilabel:`Add " +"Custom Group` :icon:`fa-caret-down` at the bottom of the list, revealing " +"further grouping options. Click :guilabel:`Start Date` from the expanded " +"list." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:64 +msgid "" +"After doing so, the data presented is grouped with the various months from " +"the previous 365 days for the rows, leaving the :guilabel:`Days In Stage` as" +" the columns." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:-1 +msgid "The pivot table showing the months averages for times in stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:71 +msgid "" +"In this example, :guilabel:`July 2024` had the longest time that applicants " +"spent in each stage, on average. In addition, the :guilabel:`Contract " +"Proposal` stage had the longest wait time in July, with an average of " +":guilabel:`31.62` days in that stage." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:75 +msgid "" +"While this report does not display the reasons applicants stayed in the " +"various stages for these lengths of time, it can be helpful to know when " +"delays occur." +msgstr "" + +#: ../../content/applications/hr/recruitment/time_in_stage.rst:79 +msgid ":doc:`Essentials reporting documentation <../../essentials/reporting>`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:5 +msgid "Referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:7 +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, and 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 **Employees**, **Recruitment**, and **Website**" +" apps must all be installed for the **Referrals** app to function." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:14 +msgid "" +"The only configurations needed for the **Referrals** app *after* it has been" +" installed, are related to the :doc:`rewards `; " +"everything else is preconfigured when Odoo **Referrals** is installed." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:18 +msgid "" +"Users with either :guilabel:`Referral User`, :guilabel:`Officer`, or " +":guilabel:`Administrator` access rights for the **Recruitment** app can " +"access the **Referrals** app. Only users with :guilabel:`Administrator` " +"access rights for the **Recruitment** app have access to the :doc:`reporting" +" ` and configuration menus. For more information on " +"users and access rights, refer to these documents: :doc:`../general/users` " +"and :doc:`../general/users/access_rights`." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:30 +msgid "" +"When opening the **Referrals** app for the first time, a preconfigured " +"onboarding script appears. This script consists of four slides, each " +"explaining the different parts of the **Referrals** app. 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:36 +msgid "" +"Each of the onboarding slides has a corresponding image and message that is " +"displayed. After reading each message, click the :guilabel:`Next` :icon:`fa-" +"angle-right` button to advance to the next slide." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:39 +msgid "The text that appears on each slide is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:41 +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:43 +msgid "" +":guilabel:`BROWSE THROUGH OPEN JOB POSITIONS, PROMOTE THEM ON SOCIAL MEDIA, " +"OR REFER FRIENDS.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:44 +msgid "" +":guilabel:`COLLECT POINTS AND EXCHANGE THEM FOR AWESOME GIFTS IN THE SHOP.`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:45 +msgid "" +":guilabel:`COMPETE AGAINST YOUR COLLEAGUES TO BUILD THE BEST JUSTICE " +"LEAGUE!`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:48 +msgid "" +"The onboarding slides will appear every time the **Referrals** app 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** app 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** " +"app is opened from that point on." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:55 +msgid "" +"At any point during onboarding, click the :guilabel:`Skip` button to open " +"the main **Referrals** dashboard." +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:62 +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:68 +msgid "Modifying onboarding slides" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:70 +msgid "" +"Onboarding slides can be modified if desired. Only users with " +":guilabel:`Administrator` rights for the **Recruitment** app 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." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:76 +msgid "" +"Make any changes to the message in the :guilabel:`Text` field. A " +":guilabel:`Company` may be selected, as well. However, if this field is " +"populated, that slide is *only* displayed for that particular company." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:81 +msgid "" +"The :guilabel:`Company` field only appears when in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:83 +msgid "" +"The image can be modified, as well. Hover over the image thumbnail in the " +"top-right corner of the form. An :icon:`fa-pencil` :guilabel:`(Edit)` icon " +"and :icon:`fa-trash-o` :guilabel:`(Clear)` icon appear. Click the :icon:`fa-" +"pencil` :guilabel:`(Edit)` 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 :icon:`fa-trash-o` :guilabel:`(Clear)` icon, then select a " +"new image using the :icon:`fa-pencil` :guilabel:`(Edit)` icon." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "An onboarding slide in edit mode, with the main fields highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:93 +msgid "" +"The sequence in which the slides appear can be changed from the *Onboarding*" +" dashboard. Click the :icon:`oi-draggable` :guilabel:`(draggable)` icon to " +"the left of the slide text, and drag the slide to the desired position." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "" +"The onboarding slides in a list, with the drag and drop arrows highlighted." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:103 +msgid "Hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:105 +msgid "" +"When a candidate referred by a user is hired, the user *\"grows their " +"superhero team\"* and adds superhero avatars to their **Referrals** " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:108 +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/referrals.rst:112 +msgid "" +"Below this message are five avatar thumbnails to choose from. If an avatar " +"has already been assigned to a referral, the thumbnail is grayed out, and " +"the name that the avatar has been chosen for appears beneath the avatar. " +"Click on an available avatar to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:116 +msgid "" +"If more than one referral was hired since completing onboarding in the " +"**Referrals** app, 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/referrals.rst:-1 +msgid "" +"The hired screen. A selection of avatars are presented to choose from, with any already\n" +"chosen are greyed out." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:126 +msgid "Modify friends" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:128 +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** app can make modifications to friends. The " +"preconfigured friends can be seen and modified by navigating to " +":menuselection:`Referrals app --> Configuration --> Friends`. Each friend's " +"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/referrals.rst:135 +msgid "" +"To modify a friend's dashboard image, thumbnail, name, or position, click on" +" an individual friend to open the referral friend form. 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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:140 +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/referrals.rst:145 +msgid "" +"If desired, both the thumbnail :guilabel:`Image` and the " +":guilabel:`Dashboard Image` can be modified. Hover over the image being " +"replaced to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and " +":icon:`fa-trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon, and a file explorer window appears. Navigate to the" +" desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:151 +#: ../../content/applications/hr/referrals.rst:220 +msgid "" +"To cancel any changes made, click the :icon:`fa-times` :guilabel:`(Discard " +"all changes)` icon to delete any changes, and revert to the original " +"content." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A friend form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:158 +#: ../../content/applications/hr/referrals.rst:192 +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** app." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:162 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:169 +msgid "Levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:171 +msgid "" +"The **Referrals** app has preconfigured 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/referrals.rst:176 +msgid "" +"Levels have no functional impact on the performance of the app. 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/referrals.rst:180 +msgid "" +"The user's current level is displayed at the top of the main **Referrals** " +"app dashboard, directly beneath their photo, in a :guilabel:`Level: #` " +"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/referrals.rst:187 +msgid "Modify levels" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:189 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** app" +" can modify levels." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:196 +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** app must be *uninstalled then reinstalled.*" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:200 +msgid "" +"The preconfigured 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/referrals.rst:206 +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, then make " +"modifications." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:209 +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/referrals.rst:215 +msgid "" +"If desired, the :guilabel:`Image` can also be modified. Hover over the image" +" to reveal an :icon:`fa-pencil` :guilabel:`(Edit)` icon and a :icon:`fa-" +"trash-o` :guilabel:`(Clear)` icon. Click the :icon:`fa-pencil` " +":guilabel:`(Edit)` icon and a file explorer window appears. Navigate to the " +"desired image file, then click :guilabel:`Open` to select it." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:-1 +msgid "A level form in edit mode." +msgstr "" + +#: ../../content/applications/hr/referrals.rst:227 +msgid "Level up" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:229 +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/referrals.rst:234 +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/referrals.rst:238 +msgid "" +"Leveling up does not cost the user any points, the user only needs to earn " +"the specified amount of points required." +msgstr "" + +#: ../../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/referrals.rst:246 +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/referrals.rst:251 +msgid ":doc:`referrals/share_jobs`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:252 +msgid ":doc:`referrals/points`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:253 +msgid ":doc:`referrals/rewards`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:254 +msgid ":doc:`referrals/alerts`" +msgstr "" + +#: ../../content/applications/hr/referrals.rst:255 +msgid ":doc:`referrals/reporting`" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:5 +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." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:8 +msgid "" +"Alerts remain on the main **Referrals** dashboard for the specified amount " +"of time configured on the individual alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "Two alert banners appear above the user's photo." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:17 +msgid "Create an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:19 +msgid "" +"Only users with *Administrator* access rights for the **Recruitment** app " +"can create alerts. To add a new alert, navigate to the " +":menuselection:`Referrals app --> Configuration --> Alerts`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:22 +msgid "" +"Click :guilabel:`New` to open a blank alert form. Enter the following " +"information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:24 +msgid "" +":guilabel:`Date From`: the date the alert starts. On this date, the alert is" +" visible on the dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:26 +msgid "" +":guilabel:`Date To`: the date the alert ends. After this date, the alert is " +"hidden from view." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:27 +msgid "" +":guilabel:`Company`: the current company populates this field, by default. " +"To modify the company the alert should be displayed for, select the desired " +"company from the drop-down menu in this field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:31 +msgid "" +"If this field remains blank, the alert is visible to everyone with access to" +" the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:34 +msgid "" +"If a company is specified, only users within that company (who also have " +"access to the **Referrals** app) see the alert. This field **only** appears " +"in a multi-company database." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:36 +msgid "" +":guilabel:`Alert`: enter the text for the alert. This message appears inside" +" the alert banner on the main **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:38 +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/referrals/alerts.rst:41 +msgid "" +":guilabel:`Not Clickable`: the alert only displays text, there is no link to" +" click." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:42 +msgid "" +":guilabel:`Go to All Jobs`: the alert contains a link that, when clicked, " +"navigates to the website with all the job positions that are currently " +"posted." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:44 +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 desired URL in " +"that field." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:-1 +msgid "An alert form completely filled in with all selections entered." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:52 +msgid "Notify users" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:54 +msgid "" +"In addition to posting an alert on the **Referrals** app, users can be " +"contacted directly via email, instead of waiting for users to view the alert" +" when they open the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:57 +msgid "" +"After :ref:`creating an alert `, click the " +":guilabel:`Send Mail` button above the alert form. This causes a " +":guilabel:`Send Mail` pop-up window to load." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:60 +msgid "" +"The currently configured users populate the :guilabel:`User` field, and the " +":guilabel:`Subject` is populated with `New Alert In Referrals App`, by " +"default." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:63 +msgid "" +"The :guilabel:`Body` is populated with `A new alert has been added to the " +"Referrals app! Check your dashboard now!`, with the word `dashboard` linked " +"to the **Referrals** app dashboard." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:66 +msgid "" +"Make any desired modifications to the email, then click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:69 +msgid "Dismiss an alert" +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:71 +msgid "" +"It is possible to dismiss an alert, if a user does not wish to see a " +"specific alert again." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:73 +msgid "" +"To dismiss an alert, click the :icon:`fa-times` :guilabel:`(remove)` icon on" +" the far-right side of the alert on the **Referrals** app dashboard, to " +"remove the alert." +msgstr "" + +#: ../../content/applications/hr/referrals/alerts.rst:76 +msgid "" +"This prevents the alert from appearing again, even when opening the " +"**Referrals** app for the first time in a new session." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:3 +msgid "Referral points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:5 +msgid "" +"The *Referrals* application allows employees to earn points that are then " +"exchanged for :doc:`rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:8 +msgid "" +"Current referral points can be viewed on the main *Referrals* app dashboard," +" which appears when the application is opened, after the :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:12 +msgid "" +"At the top, a summary of the user's current points is displayed. The left " +"side of the summary displays the :guilabel:`Total` points earned, and the " +"right side displays the points that are available :guilabel:`To Spend`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:16 +msgid "" +"To view the various referral stages, and their respective earned points, " +"click one of the referral statuses beneath the avatar. The options are: " +":guilabel:`Referrals`, :guilabel:`Ongoing`, and :guilabel:`Successful`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:20 +msgid "" +"The current number of referrals that are still active in the recruitment " +"pipeline, but have not yet been hired or refused, appear above " +":guilabel:`Ongoing`. The number of referrals that have been hired, appears " +"above :guilabel:`Successful`. The total number of referrals, both the " +"ongoing and successful referrals combined, appears above " +":guilabel:`Referrals`." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:26 +msgid "My referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:28 +msgid "" +"To see all the referrals, both ongoing and successful, click " +":guilabel:`Referrals`. The :guilabel:`My Referral` screen page displays all " +"referrals, with each individual referral housed in its own referral card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:32 +msgid "" +"A successful referral displays a white :icon:`fa-check` :guilabel:`Hired` " +"badge in the top-right corner of the card, along with a vertical green " +"stripe on the left-side of the card. Referrals that are in process have a " +"purple :guilabel:`In Progress` badge in the top-right corner." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:36 +msgid "" +"Each referral card lists the name of the applicant, the subject/application " +"title as it appears on the applicant card in the *Recruitment* app, the name" +" of the job position, the person responsible for filling the role (i.e. the " +"recruiter), and the points earned." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:40 +msgid "" +"For referrals that have been hired, the selected avatar also appears on the " +"card." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:-1 +msgid "Two referral cards, one hired and one in-progress." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:47 +msgid "Points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:49 +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/referrals/points.rst:53 +msgid "" +"On each individual referral card, beneath the points earned, is a progress " +"bar 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/referrals/points.rst:57 +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 :icon:`fa-check` " +":guilabel:`(checkmark)` appears next to the stage." +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:62 +msgid "The preconfigured point structure for referrals is as follows:" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:64 +msgid ":guilabel:`Initial Qualification`: 1 point" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:65 +msgid ":guilabel:`First Interview`: 20 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:66 +msgid ":guilabel:`Second Interview`: 9 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:67 +msgid ":guilabel:`Contract Proposal`: 5 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:68 +msgid ":guilabel:`Contract Signed`: 50 points" +msgstr "" + +#: ../../content/applications/hr/referrals/points.rst:70 +msgid "" +"The default total points earned for a referral that is hired is 85 points. " +"Modifications of the points earned for each stage are made in the " +"*Recruitment* application. Refer to the :ref:`Recruitment " +"` documentation to modify the points for each " +"stage." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:5 +msgid "" +"The reporting function in the **Referrals** app helps recruiters and " +"managers learn where applicants are applying from, when referred by a " +"current employee. Additionally, the reporting feature shows the number of " +"applicants hired, refused, and still in the recruitment pipeline, for each " +"medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:10 +msgid "" +"Only users with *Administrator* rights for the **Recruitment** app have " +"access to the reporting feature in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:14 +msgid "Employees referral analysis report" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:16 +msgid "" +"To access the *Employees Referral Analysis* report, navigate to " +":menuselection:`Referrals app --> Reporting`. This loads the " +":guilabel:`Employees Referral Analysis` report, in a default :icon:`fa-bar-" +"chart` :guilabel:`Bar Chart`." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:20 +msgid "" +"The graph is presented in a :icon:`fa-database` :guilabel:`Stacked` view, " +"with the number of referrals on the y-axis, and the source, referred to as " +"the :guilabel:`Medium`, of the applicant (e.g.: *Facebook*, *LinkedIn*, " +"*Email*, etc.) on the x-axis. If a medium does **not** appear on the report," +" that indicates there are no referrals from that particular medium." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:25 +msgid "" +"Referral amounts for all stages are displayed, including :guilabel:`Not " +"Hired` (refused), :guilabel:`In Progress`, and :guilabel:`Hired`. The " +"default filter is set to the current month." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:28 +msgid "" +"Hover over any bar to view a popover containing specific data for that " +"particular bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:30 +msgid "" +"In this view, it is clear which :guilabel:`Medium` is the most successful." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:33 +msgid "" +"In this example, both :guilabel:`Email` and :guilabel:`LinkedIn` are the " +"mediums with the most referrals, but :guilabel:`Email` has the most " +"referrals that were hired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:0 +msgid "The default report in the Referrals app." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:40 +msgid "Use case: hired referrals" +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:42 +msgid "" +"One way to use the reporting feature is to assess which employees are " +"referring the highest quality applicants. This is done by examining how many" +" of their referrals go on to become employees." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:45 +msgid "" +"In this example, data is examined to determined which employee has the " +"highest number of hired referrals for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:48 +msgid "" +"To view this information, first click the :icon:`oi-view-pivot` " +":guilabel:`(Pivot)` icon in the upper-right corner. Next, remove the current" +" filter in the search bar." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:51 +msgid "" +"Click the :icon:`fa-caret-down` :guilabel:`(down arrow)` in the search bar " +"to reveal a drop-down menu. Click :guilabel:`Date` in the :icon:`fa-filter` " +":guilabel:`Filters` column, revealing a drop-down menu of available time " +"periods, and click the current year (in this example, :guilabel:`2024`)." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:56 +msgid "" +"Next, click :guilabel:`Measures` :icon:`fa-caret-down`, then deselect " +":guilabel:`Earned Points` and :guilabel:`Employee Referral Refused` to hide " +"those metrics. Click anywhere on the screen to close the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:60 +msgid "" +"The information displayed shows how many total applicants each employee " +"referred, and how many of those applicants were hired, for the current year." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:63 +msgid "" +"In this example, it can be determined that :guilabel:`Bob Wilson` is the " +"most successful referrer, with three hired referrals, and nine total " +"referred applicants. Additionally, :guilabel:`Mitchell Admin` has the lowest" +" performance in terms of referrals, as he has only one applicant, and no " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:67 +msgid "" +"This information can be helpful to the recruitment team, so they can " +"determine the most active referrers in the company, and who is the most " +"successful in terms of hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:-1 +msgid "" +"The customized report showing which employees have the most referrals and " +"hires." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:74 +msgid "" +"The pivot table can be inserted into a new or existing :doc:`spreadsheet " +"<../../productivity/spreadsheet/insert>`, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:77 +msgid "" +"To do so, click the :guilabel:`Insert in Spreadsheet` button right above the" +" chart. A pop-up window appears, asking which spreadsheet to insert the " +"pivot chart into. Select the desired spreadsheet or dashboard from the " +"presented options. Alternatively, select :guilabel:`Blank Spreadsheet` to " +"create a new one." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:82 +msgid "" +"Click :guilabel:`Confirm`, and the selected spreadsheet loads, with the new " +"table in it." +msgstr "" + +#: ../../content/applications/hr/referrals/reporting.rst:84 +msgid "" +"The spreadsheet is stored in the **Documents** application. This application" +" **must** be installed to use the :guilabel:`Insert in Spreadsheet` option." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:3 +msgid "Rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:5 +msgid "" +"After employees have successfully earned referral points, they can exchange " +"their points by purchasing rewards in Odoo's **Referrals** application. " +"Rewards **must** be :ref:`created and configured ` before " +"employees can :ref:`redeem points for rewards `." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:13 +msgid "Create rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:15 +msgid "" +"Rewards are the only configurations needed when setting up the **Referrals**" +" application." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:17 +msgid "" +"Only users with :guilabel:`Administrator` rights for the **Recruitment** " +"application can create or modify rewards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:21 +msgid ":doc:`../../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:23 +msgid "" +"To add rewards, navigate to :menuselection:`Referrals app --> Configuration " +"--> Rewards`. Click :guilabel:`New`, and a reward form loads. Enter the " +"following information on the form:" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:26 +msgid "" +":guilabel:`Product Name`: enter the name as it should appear for the reward." +" This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:28 +msgid "" +":guilabel:`Cost`: enter the amount of points required to redeem the reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:29 +msgid "" +":guilabel:`Company`: using the drop-down menu, select the company the reward" +" is configured for. If a reward is available for multiple companies, each " +"company **must** configure a reward for their specific company. This field " +"**only** appears if in a multi-company environment; if this field appears, " +"it is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:35 +msgid "" +"A corporation with three different companies offers a gift card as a reward." +" In the database, there are three separate rewards listed for a gift card, " +"one for each of the three companies." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:38 +msgid "" +":guilabel:`Gift Responsible`: using the drop-down menu, select the person " +"responsible for procuring and delivering the reward to the recipient. This " +"person is alerted when the reward is bought in the **Referrals** app, so " +"they know when to deliver the reward to the recipient." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:41 +msgid "" +":guilabel:`Photo`: add a photo of the reward, which appears on the rewards " +"page. Hover over the image box in the top-right corner (a square with a " +"camera and plus sign inside it), and a :icon:`fa-pencil` " +":guilabel:`(pencil)` icon appears. Click the :icon:`fa-pencil` " +":guilabel:`(pencil)` icon to select and add a photo to the reward form. Once" +" a photo is added, hovering over the image reveals two icons instead of one:" +" a :icon:`fa-pencil` :guilabel:`(pencil)` icon and a :icon:`fa-trash-o` " +":guilabel:`(trash can)` icon. Click the :icon:`fa-trash-o` :guilabel:`(trash" +" can)` icon to delete the currently selected image." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:48 +msgid "" +":guilabel:`Description` tab: type in the description for the reward. This is" +" visible on the reward card, beneath the title. This field is required." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:-1 +msgid "A filled out reward form with all details entered." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:55 +msgid "" +"It is advised to enter a :guilabel:`Cost` and add a :guilabel:`Photo`. If a " +"cost is not entered, the default cost is listed as zero, which would list " +"the reward as free in the reward shop. If a photo is not selected, a " +"placeholder icon is displayed on the rewards page." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:62 +msgid "Redeem rewards" +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:64 +msgid "" +"In order to redeem a reward, points must be earned. These points can then be" +" used to purchase a reward." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:67 +msgid "" +"To purchase a reward, click the :guilabel:`Rewards` button on the main " +":guilabel:`Referrals` dashboard. All the configured rewards are listed in " +"individual reward cards." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:70 +msgid "" +"The required point amount needed to purchase a reward is listed in the top-" +"right corner of the card." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:72 +msgid "" +"If the user has enough points to purchase a reward, a :icon:`fa-shopping-" +"basket` :guilabel:`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 :icon:`fa-" +"shopping-basket` :guilabel:`Buy` button." +msgstr "" + +#: ../../content/applications/hr/referrals/rewards.rst:77 +msgid "" +"Click the :icon:`fa-shopping-basket` :guilabel:`Buy` button on a reward to " +"purchase it. A :guilabel:`Confirmation` pop-up window 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/referrals/rewards.rst:82 +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/referrals/rewards.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/referrals/share_jobs.rst:3 +msgid "Share job positions" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:5 +msgid "" +"In Odoo **Referrals**, users can earn referral points by sharing job " +"positions with potential applicants. Individual job positions can be shared " +"in several ways: via :ref:`email `, :ref:`SMS " +"`, :ref:`WhatsApp `, a :ref:`tracking " +"link `, and various :ref:`social media platforms " +"`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:10 +msgid "" +"Additionally, *all* job positions can be :ref:`shared via email " +"`, instead of sharing individual job positions." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:14 +msgid "" +"Sharing jobs can **only** occur after :ref:`onboarding " +"` slides have been viewed or skipped." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:20 +msgid "View all jobs" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:22 +msgid "" +"To see all job positions that are actively recruiting candidates, click the " +":guilabel:`View Jobs` button on the main **Referrals** app dashboard. This " +"presents all job positions, with each job presented with its own card." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.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/referrals/share_jobs.rst:30 +msgid "Each job position card contains the following information:" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:32 +msgid "" +"The title of the job position. This information is taken from the *Job " +"Position* field of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:34 +msgid "" +"The number of :guilabel:`Open Positions` being recruited. This information " +"is taken from the *Expected New Employees* field of the *Recruitment* tab of" +" the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:36 +msgid "" +"The :doc:`points ` a user earns when an applicant applies for the " +"position." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:37 +msgid "" +"The job description detailing the job position. This information is taken " +"from the *Job Position* tab of the job form." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:41 +msgid "" +"Only published job positions are 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/referrals/share_jobs.rst:45 +msgid "Share an individual job" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:47 +msgid "" +"To share an individual job position, first click the :guilabel:`View Jobs` " +"button on the main **Referrals** app dashboard. This presents a list of all " +"currently published jobs. From this page, an individual job can be shared " +"with someone using one of the methods below." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:56 +msgid "" +"To share an individual job position via email, click the :icon:`fa-" +"envelope-o` :guilabel:`Send Email` button on the specific job position card." +" A preconfigured email template appears in a pop-up window, using the " +":guilabel:`Send Job Offer by Mail` template. Enter the recipient's email " +"address in the :guilabel:`Email` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:61 +msgid "" +"The :guilabel:`Subject` and :guilabel:`Body` are populated using a default " +"template. The :guilabel:`Subject` `Job for you` is present, by default, but " +"can be modified, if desired." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:64 +msgid "" +"The specific title of the job position populates the *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." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:68 +msgid "" +"When the prospective employee receives the email, the link sends them to the" +" job position page, where they can apply for the position, and the person " +"who referred them is tracked in the **Referrals** app." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:72 +msgid "" +"If desired, add any text or closing salutation to the email body. When all " +"edits have been made, click :guilabel:`Send Mail` to send the email, or " +"click :guilabel:`Cancel` to close the pop-up window." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:-1 +msgid "Referral email pop-up window with the email message inside it." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:84 +msgid "" +"To share an individual job position with someone via SMS (text message), " +"click the :icon:`fa-mobile` :guilabel:`Send SMS` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by SMS` pop-up " +"window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:89 +msgid "" +"Modify the prepopulated :guilabel:`Body` message, if desired, then click the" +" :guilabel:`Send SMS` button to send the message, or click " +":guilabel:`Cancel` to close the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:101 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:103 +msgid "" +"To share an individual job position with someone via WhatsApp, click the " +":icon:`fa-whatsapp` :guilabel:`Send WhatsApp` button on the specific job " +"position card. A preconfigured :guilabel:`Send Job Offer by WhatsApp` pop-up" +" window appears. Enter the recipient's mobile number in the " +":guilabel:`Recipient` field." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:108 +msgid "" +"Modify the default message, if desired, then click the :guilabel:`Send " +"WhatsApp` button to send the message, or click :guilabel:`Cancel` to close " +"the pop-up window and cancel the message." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:112 +msgid "" +"To send WhatsApp messages, WhatsApp must be configured in Odoo. For more " +"information, refer to the :doc:`../../productivity/whatsapp` documentation." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:116 +msgid "Job page" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:118 +msgid "" +"To see all the details for a job position, click the :icon:`fa-globe` " +":guilabel:`Job Page` button on the specific card. Doing so 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/referrals/share_jobs.rst:125 +msgid "Share now" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:127 +msgid "" +"To share the job position with a customized tracking link, click the " +":icon:`fa-chain` :guilabel:`Share Now` button to copy the link. A pop-up " +"window in the corner of the computer loads, stating `Referral link: (link to" +" Job Position) has been copied to clipboard`." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:131 +msgid "Next, share the link with the prospective employee." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:136 +msgid "Share a job via social media" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:138 +msgid "" +"Other than sending an email, SMS, WhatsApp message, or sharing a tracking " +"link, job positions can be shared via social media platforms (:ref:`Facebook" +" `, :ref:`X `, and :ref:`LinkedIn " +"`. On each job position card are the three corresponding" +" social media icons that can be used to share the job position, keeping " +"track of applicants in the **Referrals** application." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:147 +msgid "Facebook" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:149 +msgid "" +"To share the job position using Facebook, click the :icon:`fa-facebook` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:152 +msgid "" +"If the user is already logged into Facebook, when the :icon:`fa-facebook` " +":guilabel:`Share Now` button is clicked, Facebook loads in a new tab, where " +"a :guilabel:`Create post` pop-up window loads with the tracking link " +"attached." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:156 +msgid "" +"Type in any additional information to add to the post, then share the job " +"position using the available options in Facebook." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:160 +msgid "" +"To share the job via Facebook,first, the user **must** be logged into " +"Facebook. If the user is *not* already logged in, when the :icon:`fa-" +"facebook` :guilabel:`Share Now` button is clicked, a new tab loads, stating " +"`You are not logged in. Please login and try again.`" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:167 +msgid "X (formerly Twitter)" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:169 +msgid "" +"To share a job position on X, click the :guilabel:`X Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:171 +msgid "" +"If the user is already signed-in to X, when the :guilabel:`X Share Now` " +"button is clicked, an X page loads in a new tab with a pre-populated message" +" ready to post, in a draft pop-up window. If the user is *not* already " +"signed-in, a sign-in screen loads instead, prompting the user to first sign-" +"in to X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:176 +msgid "" +"Type in any additional information, or make any edits to the default " +"message, then share using the available options in X." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:182 +msgid "LinkedIn" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:184 +msgid "" +"To share a job position on LinkedIn, click the :icon:`fa-linkedin` " +":guilabel:`Share Now` button." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:186 +msgid "" +"If the user is already logged into LinkedIn, when the :icon:`fa-linkedin` " +":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/referrals/share_jobs.rst:191 +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/referrals/share_jobs.rst:194 +msgid "" +"Type in any additional information, or make any edits to the message or " +"post, then share using the available options in LinkedIn." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:200 +msgid "Share job list" +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:202 +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 :menuselection:`Referrals` main 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/referrals/share_jobs.rst:207 +msgid "" +"Enter the email address in the :guilabel:`Email` field. The email can be " +"sent to multiple recipients by separating each email address with a comma " +"followed by a single space. The :guilabel:`Subject` is preconfigured with " +":guilabel:`Job for you`, but can be edited. The email :guilabel:`Body` is " +"also populated with preconfigured text." +msgstr "" + +#: ../../content/applications/hr/referrals/share_jobs.rst:212 +msgid "" +"The link to all active job positions is a tracking link to a complete list " +"of all job positions currently being recruited for. Add any additional text " +"and make any edits to the message body, if necessary. Then, click " +":guilabel:`Send Mail` to send the email. This sends the message, and closes " +"the window." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:7 +msgid "" +"Odoo's **Time Off** application serves as a centralized hub for all time-" +"off-related information. This application manages requests, balances, " +"allocations, approvals, and reports." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:10 +msgid "" +"Users can :doc:`request time off <../hr/time_off/request_time_off>`, and see" +" an overview of their requests and time off balances. Managers can " +":doc:`allocate time off ` to individuals, teams, or " +"the whole company, and :ref:`approve time off requests `." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:15 +msgid "" +"Detailed :ref:`reports ` can be run to see how much time" +" off (and what kinds of time off) are being used, :ref:`accrual plans " +"` can be created, and :ref:`public holidays " +"` can be set." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:20 +msgid "" +"Be advised, only users with specific access rights can see all aspects of " +"the **Time Off** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:22 +msgid "" +"All users can access the *My Time Off* and *Overview* sections of the **Time" +" Off** app. All other sections require specific access rights." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:25 +msgid "" +"To better understand how access rights affect the **Time Off** app, refer to" +" the :doc:`employees/new_employee` document, specifically the section about " +"configuring the *Work Information* tab." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:30 +msgid ":doc:`../general/users/access_rights`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:35 +msgid "" +"In order to allocate time off to employees, and for employees to request and" +" use their time off, the various time off types must be configured first, " +"then allocated to employees (if allocation is required)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:44 +msgid "" +"To view the currently configured time off types, navigate to " +":menuselection:`Time Off app --> Configuration --> Time Off Types`. The time" +" off types are presented in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:47 +msgid "" +"The **Time Off** app comes with four preconfigured time off types: " +":guilabel:`Paid Time Off`, :guilabel:`Sick Time Off`, :guilabel:`Unpaid`, " +":guilabel:`Compensatory Days`, and :guilabel:`Extra Hours`. These can be " +"modified to suit business needs, or used as-is." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:52 +msgid "Create time off type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:54 +msgid "" +"To create a new time off type, navigate to :menuselection:`Time Off app --> " +"Configuration --> Time Off Types`. From here, click the :guilabel:`New` " +"button to reveal a blank time off type form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:57 +msgid "" +"Enter the name for the particular type of time off in the blank line at the " +"top of the form, such as `Vacation` or `Bereavement`. Then, enter the " +"following information on the form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:61 +msgid "" +"The only **required** fields on the time off type form are the name of the " +":guilabel:`Time Off Type`, the :guilabel:`Take Time Off In`, and the " +":guilabel:`Kind of Time Off`. In addition, the :guilabel:`Time Off Requests`" +" and :guilabel:`Allocation Requests` sections **must** be configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:67 +msgid "Time off requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:69 +msgid "" +"This section determines how approvals are handled for time off requests for " +"this time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:71 +msgid "" +":guilabel:`Approval`: select what specific kind of approval is required for " +"the time off type. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:74 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting this " +"type of time off. The time off request is automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:76 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the time off request. This " +"option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:79 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:82 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:87 +msgid "Allocation requests section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:89 +msgid "" +"This section determines how allocation requests are handled for this time " +"off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:91 +msgid "" +":guilabel:`Requires allocation`: If the time off must be allocated to " +"employees, select :guilabel:`Yes`. If the time off can be requested without " +"time off being previously allocated, select :guilabel:`No Limit`. If " +":guilabel:`No Limit` is selected, the following options do not appear on the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:95 +msgid "" +":guilabel:`Employee Requests`: Select :guilabel:`Extra Days Requests " +"Allowed` if the employee is able to request more time off than was " +"allocated." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:98 +msgid "" +"If employees should **not** be able to make requests for more time off than " +"what was allocated, select the :guilabel:`Not Allowed` option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:102 +msgid "" +"Ten days are allocated to the employee for this particular type of time off," +" and the :guilabel:`Extra Days Requests Allowed` option is enabled. The " +"employee wants to take a vacation for twelve days. They may submit a request" +" for two additional days, since the :guilabel:`Extra Days Requests Allowed` " +"option is enabled." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:108 +msgid "" +"It is important to note that requesting additional time off does **not** " +"guarantee that time off is granted." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:111 +msgid "" +":guilabel:`Approval`: Select the type of approvals required for the " +"allocation of this particular time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:114 +msgid "" +":guilabel:`No Validation`: No approvals are required when requesting " +"additional allocations for the time off type. The allocation request is " +"automatically approved." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:116 +msgid "" +":guilabel:`By Time Off Officer`: Only the specified :ref:`Time Off Officer " +"`, set on this form in the :guilabel:`Notified " +"Time Off Officer` field, is required to approve the allocation request. This" +" option is selected, by default." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:119 +msgid "" +":guilabel:`By Employee's Approver`: Only the employee's specified approver " +"for time off, which is set on the *Work Information* tab on the " +":ref:`employee's form `, is required to approve the" +" allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:122 +msgid "" +":guilabel:`By Employee's Approver and Time Off Officer`: Both the employee's" +" :ref:`specified time off approver ` and the " +":ref:`Time Off Officer ` are required to approve " +"the allocation request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:128 +msgid "Configuration section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:130 +msgid "" +"This section determines all other details regarding the time off type, aside" +" from approvals and allocations. This includes how the time off must be " +"taken (hours, half days, or days), if the time off is visible to other " +"users, and how the time off affects the **Payroll** app." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:136 +msgid "" +":guilabel:`Notified Time Off Officer`: Select the user who is notified and " +"responsible for approving requests and allocations for this specific type of" +" time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:138 +msgid "" +":guilabel:`Take Time Off in`: Select the format the time off is requested in" +" from the drop-down menu. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:141 +msgid "" +":guilabel:`Day`: if time off can only be requested in full day increments (8" +" hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:142 +msgid "" +":guilabel:`Half Day`: if time off can only be requested in half day " +"increments (4 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:143 +msgid ":guilabel:`Hours`: if the time off can be taken in hourly increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:147 +msgid "" +":guilabel:`Deduct Extra Hours`: Enable this option if the time off request " +"should factor in any extra time accrued by the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:151 +msgid "" +"If an employee works two extra hours for the week, and requests five hours " +"of time off, the request would be for three hours, since the two extra " +"worked hours are used first, and deducted from the request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:155 +msgid "" +":guilabel:`Public Holiday Included`: Enable this option if public holidays " +"should be excluded from a time off request." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:159 +msgid "" +"An employee in the United States requests time off for the week of July 4th," +" for a total of five days. Since the 4th of July is a holiday in the United " +"States, the time off request is automatically modified for four days off " +"instead of five. That is because the holiday is included, and the user does " +"not need to use their own vacation time for a public holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:164 +msgid "" +"This option reduces extra work for users, enabling them to make only one " +"time off request for the entire week, instead of making two separate " +"requests, one for the days *before* the holiday, and another one for the " +"days *after* the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:168 +msgid "" +":guilabel:`Allow To Attach Supporting Document`: Enable this option to allow" +" the employee to attach documents to the time off request. This is useful in" +" situations where documentation is required, such as long-term medical " +"leave." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:171 +msgid "" +":guilabel:`Kind of Time Off`: From the drop-down menu, select the type of " +"time off, either :guilabel:`Worked Time` or :guilabel:`Absence`. " +":guilabel:`Worked Time` indicates the time off taken counts toward worked " +"time for any type of accrual the employee is working towards, whereas " +":guilabel:`Absence` does not count toward any type of accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:175 +msgid "" +":guilabel:`Company`: If multiple companies are created in the database, and " +"this time off type only applies to one company, select the company from the " +"drop-down menu. If this field is left blank, the time off type applies to " +"all companies in the database. This field **only** appears in a multi-" +"company database." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:181 +msgid "Negative cap section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:183 +msgid "" +"Enable the :guilabel:`Allow Negative Cap` option if employees are able to " +"request more time off than they currently have, allowing a negative balance." +" If enabled, an :guilabel:`Maximum Excess Amount` field appears. In this " +"field, enter the maximum amount of negative time allowed, in days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:188 +msgid "" +"Sara currently has three days of the time off type `Vacation`. She is " +"planning a trip that requires five days of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:191 +msgid "" +"The `Vacation` time off type has the :guilabel:`Allow Negative Cap` option " +"enabled, and the :guilabel:`Maximum Excess Amount` is set to five." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:194 +msgid "" +"These settings allow Sara to submit a request for five days of the " +"`Vacation` time off type. If approved, her `Vacation` time off balance will " +"be negative two (-2) days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The top half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:202 +msgid "Payroll section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:204 +msgid "" +"If the time off type should create :doc:`../hr/payroll/work_entries` in the " +"**Payroll** app, select the :guilabel:`Work Entry Type` from the drop-down " +"list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:208 +msgid "Timesheets section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:211 +msgid "" +"The :guilabel:`Timesheets` section only appears if the user is in developer " +"mode. Refer to the :ref:`developer-mode` document for details on how to " +"access the developer mode." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:214 +msgid "" +"When an employee takes time off, and is also using timesheets, Odoo creates " +"entries in the **Timesheets** app for the time off. This section defines how" +" they are entered." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:217 +msgid "" +":guilabel:`Project`: Select the project the time off type entries appear in." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:218 +msgid "" +":guilabel:`Task`: Select the task that appears in the timesheet for this " +"time off type. The default options are: :guilabel:`Time Off`, " +":guilabel:`Meeting`, or :guilabel:`Training`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:222 +msgid "Display option section" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:224 +msgid "" +":guilabel:`Color`: Select a color to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:225 +msgid "" +":guilabel:`Cover Image`: Select an icon to be used in the **Time Off** app " +"dashboard." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The lower half of the time off type form, with all the information filled out for sick time\n" +"off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:234 +msgid "Accrual plans" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:236 +msgid "" +"Some time off is earned through an accrual plan, meaning that for every " +"specified amount of time an employee works (hour, day, week, etc), they earn" +" or *accrue* a specified amount of time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:240 +msgid "" +"If an employee accrues a vacation day for every week they work, they would " +"earn 0.2 vacation days for each hour they work. At the end of a forty hour " +"work week, they would earn one whole vacation day (8 hours)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:245 +msgid "Create accrual plan" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:247 +msgid "" +"To create a new accrual plan, navigate to :menuselection:`Time Off app --> " +"Configuration --> Accrual Plans`. Then, click the :guilabel:`New` button, " +"which reveals a blank accrual plan form." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:252 +msgid ":guilabel:`Name`: Enter the accrual plan name." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:253 +msgid "" +":guilabel:`Accrued Gain Time`: Select when the employee begins to accrue " +"time off, either :guilabel:`At the start of the accrual period` or " +":guilabel:`At the end of the accrual period`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:255 +msgid "" +":guilabel:`Carry-Over Time`: Select when the employee received previously " +"earned time. The options are:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:258 +msgid "" +":guilabel:`At the start of the year`: Select this if the accrual rolls over " +"on January 1 of the upcoming year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:260 +msgid "" +":guilabel:`At the allocation date`: Select this if the accrual rolls over as" +" soon as time is allocated to the employee." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:262 +msgid "" +":guilabel:`Other`: Select this option if neither of the other two options " +"are applicable. When selected, a :guilabel:`Carry-Over Date` field appears. " +"Select the date using the two drop-down menus, one for the day and one for " +"the month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:266 +msgid "" +":guilabel:`Based on worked time`: Enable this option if time off accrual is " +"determined by the employee's worked hours. Days **not** considered as worked" +" time do **not** contribute to the accrual plan in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:271 +msgid "" +"An employee is granted time off from an accrual plan configured to accrue " +"one day of vacation for every five days worked. The accrual plan is based on" +" the employee's worked time (the :guilabel:`Based on worked time` checkbox " +"is ticked), which means they **only** earn vacation time for the five " +"weekdays they work, *not* the entire seven day week period." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:276 +msgid "" +"The employee works standard 40-hour weeks. According to the accrual plan, " +"they should earn four vacation days per month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:279 +msgid "" +"The employee takes five days off using a :ref:`time off type ` with the :guilabel:`Kind of Time Off` set as an " +":guilabel:`Absence`. Because the plan grants vacation only for worked time, " +"those five days do not count toward accrual." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:283 +msgid "" +"As a result, the employee accrues only three vacation days that month " +"instead of four." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:285 +msgid "" +":guilabel:`Milestone Transition`: This field is **only** visible after a " +"minimum of two :ref:`rules ` have been configured on the " +"accrual plan. This selection determines when employees move up to a new " +"milestone. If they qualify to change milestones in the middle of a pay " +"period, decide whether the employee changes milestones " +":guilabel:`Immediately` or :guilabel:`After this accrual's period` (after " +"the current pay period)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:290 +msgid "" +":guilabel:`Company`: This field **only** appears in a multi-company " +"database. Using the drop-down menu, select the company the accrual plan " +"applies to. If left blank, the accrual plan is available for all companies." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "An accrual plan form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:302 +msgid "" +"Rules must be created in order for employees to accrue time off from the " +"accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:304 +msgid "" +"To create a new rule, click the :guilabel:`New Milestone` button in the gray" +" :guilabel:`Rules` section, and a :guilabel:`Create Milestone` modal form " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:311 +msgid "" +":guilabel:`Employee accrue`: Select the parameters for earned time off in " +"this section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:313 +msgid "" +"First, select either :guilabel:`Days` or :guilabel:`Hours` for the increment" +" of accrued time using the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:316 +msgid "" +"Next, enter the numerical amount of the selected parameter that is accrued. " +"The numerical format is `X.XXXX`, so that partial days or hours can also be " +"configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:319 +msgid "" +"Last, select how often the time is accrued using the drop-down menu. The " +"default options are :guilabel:`Hourly`, :guilabel:`Daily`, " +":guilabel:`Weekly`, :guilabel:`Twice a month`, :guilabel:`Monthly`, " +":guilabel:`Twice a year`, and :guilabel:`Yearly`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:323 +msgid "" +"Depending on which option is selected, additional fields may appear. For " +"example, if :guilabel:`Twice a month` is selected, two additional fields " +"appear, to specify the two days of each month the milestone occurs." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:326 +msgid "" +":guilabel:`Cap accrued time`: If there is a maximum amount of time the " +"employee can accrue with this plan, enable this option." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:329 +msgid "" +"When enabled, two additional fields appear to the right of the checkbox. The" +" second field is populated with either :guilabel:`Days` or " +":guilabel:`Hours`, matching the selection made in the :ref:`Employee Accrue " +"` section." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:333 +msgid "" +"Enter a numerical value in the first field to specify the maximum amount of " +"time that can be accrued, in the specified increments." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:335 +msgid "" +":guilabel:`Start Accruing`: Enter the number and value of the time period " +"that must pass before the employee starts to accumulate time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:338 +msgid "" +"Use the first field to enter a numerical value, then set the second field to" +" the desired time increment (either :guilabel:`Days`, :guilabel:`Months`, or" +" :guilabel:`Years`)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:340 +msgid "" +":guilabel:`Carry over`: select how any unused time off is handled. The " +"options are either:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:342 +msgid "" +":guilabel:`None. Accrued time reset to 0`: Any unused time off is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:343 +msgid "" +":guilabel:`All accrued time carried over`: All unused time off is rolled " +"over to the next calendar year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:345 +msgid "" +":guilabel:`Carry over with a maximum`: Unused time off is rolled over to the" +" next calendar year, but there is a cap. An :guilabel:`Up to` field appears " +"if this is selected." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:348 +msgid "" +"Enter the maximum number of :guilabel:`Hours` or :guilabel:`Days` that can " +"roll over to the following year. The presented time increment is determined " +"by how the :ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:352 +msgid "Any time off beyond this parameter is lost." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:355 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, that rule *overrides* the :guilabel:`Carry-Over Time` set on " +"the accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:358 +msgid "" +"If a company creates an accrual plan, granting employees time off " +":guilabel:`At the start of the accrual period` (i.e., the beginning of the " +"year), and sets the :guilabel:`Carry-Over Time` on the *accrual plan* to " +":guilabel:`At the start of the year`, it allows unused vacation time to " +"rollover to the following year." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:363 +msgid "" +"Then, the company adds rules to the accrual plan, allocating five days of " +"vacation, annually, on the first of the year (one week of vacation allocated" +" on January 1st)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:366 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrual time " +"reset to 0` on the :guilabel:`Create Milestone` pop-up for, any unused " +"vacation time *does not* carry over, even though on the :guilabel:`Accrual " +"Plan` form, the :guilabel:`Carry-Over Time` is set to :guilabel:`At the " +"start of the year`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:371 +msgid "" +"The carry over set on the *rule* takes precedence over the carry over set on" +" the *accrual plan form*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:374 +msgid "" +":guilabel:`Milestone cap`: Tick this checkbox to set a limit on the total " +"amount of time that can be accrued every calendar year. Enter the total " +"maximum number of :guilabel:`Hours` or :guilabel:`Days` the employee can " +"accrue during a year. The presented time increment is determined by how the " +":ref:`Employee Accrue ` section is configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:379 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Milestone cap` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:381 +msgid "" +":guilabel:`Carry Over Validity`: Tick this checkbox to set a time-limit on " +"how long the employee has to use any rolled over time off. First, set the " +"second field to the desired time-period using the drop-down menu, either " +":guilabel:`Days` or :guilabel:`Months`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:385 +msgid "" +"Next, enter the maximum number of :guilabel:`Days` or :guilabel:`Months` the" +" employee has to use their rolled over time off. After that time period " +"passes, any unused rolled over time will expire." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:389 +msgid "" +"If the :guilabel:`Carry over` field is set to :guilabel:`None. Accrued time " +"reset to 0`, the :guilabel:`Carry Over Validity` field does not appear." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:392 +msgid "" +"Once the form is completed, click :guilabel:`Save & Close` to save the " +":guilabel:`Create Milestone` form, and close the modal, or click " +":guilabel:`Save & New` to save the form and create another milestone. Add as" +" many milestones as desired." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:397 +msgid "" +"This milestone form is configured so the employee earns five days a year. " +"They start to earn this time yearly, on January 1st." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:400 +msgid "" +"The employee can never accrue more than 120 days of time off with this " +"accrual plan. Anytime they have 120 days banked, they will stop accruing " +"more time off." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:403 +msgid "" +"Additionally, they can roll over up to 100 days of time off to the next " +"year, and they have three months to use that rollover time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:406 +msgid "" +"Note that due to the :guilabel:`Capped accrued time` of 120 days, the " +"employee cannot carry over any time off that exceeds 120 days in total." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:0 +msgid "A milestone form with all the entries filled out." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:415 +msgid "Public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:417 +msgid "" +"Since holidays vary from country to country, or even city to city, there are" +" no public holidays preconfigured in Odoo. To observe public or national " +"holidays, and provide extra days off as holidays to employees, configure the" +" observed public holidays in Odoo." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:421 +msgid "" +"It is important to configure public holidays in Odoo, so employees are aware" +" of the days they have off, and do not request time off on days that are " +"already set as a public holiday (non-working days)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:425 +msgid "" +"Additionally, all public holidays configured in the **Time Off** app are " +"also reflected in any app that uses working schedules, such as **Calendar**," +" **Planning**, **Manufacturing**, and more." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:428 +msgid "" +"Due to Odoo's integration with other apps that use working schedules, it is " +"considered best practice to ensure *all* public holidays are configured." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:432 +msgid "Create public holidays" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:434 +msgid "" +"To create a public holiday, navigate to :menuselection:`Time Off app --> " +"Configuration --> Public Holidays`. All currently configured public holidays" +" appear in a default list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:437 +msgid "" +"Click the :guilabel:`New` button, and a new line appears at the bottom of " +"the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:439 +#: ../../content/applications/hr/time_off.rst:501 +msgid "Enter the following information on that new line:" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:441 +msgid ":guilabel:`Name`: Enter the name of the holiday." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:442 +msgid "" +":guilabel:`Company`: If in a multi-company database, the current company " +"populates this field by default. It is **not** possible to edit this field." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:446 +msgid "" +"The :guilabel:`Company` field is hidden, by default. To view this field, " +"click the :icon:`oi-settings-adjust` :guilabel:`(settings adjusts)` icon in " +"the top-right corner of the list, to the far-right of the column titles, and" +" activate the :guilabel:`Company` selection from the drop-down menu that " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:451 +msgid "" +":guilabel:`Start Date`: Using the date and time picker, select the date and " +"time the holiday starts, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date. The start time is " +"set according to the start time for the company (according to the " +":ref:`working schedules `). If the user's computer is" +" set to a different time zone, the start time is adjusted accordingly, " +"compared to the company's time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:456 +msgid "" +":guilabel:`End Date`: Using the date and time picker, select the date and " +"time the holiday ends, then click :icon:`fa-check` :guilabel:`Apply`. By " +"default, this field is configured for the current date, and the time is set " +"to the end time for the company (according to the :ref:`working schedules " +"`). If the user's computer is set to a different time" +" zone, the start time is adjusted accordingly, compared to the company's " +"time zone." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:463 +msgid "" +"A company located in San Francisco operates from 9:00 AM - 6:00 PM, with an " +"eight hour work day and one hour lunch break." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:466 +msgid "" +"For a user in New York, with a computer time zone set to Eastern Standard " +"Time, a created public holiday displays a start time of 12:00 PM - 9:00 PM, " +"accounting for the three hour time zone difference." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:470 +msgid "" +"Similarly, a user located in Los Angeles, with a computer time zone set to " +"Pacific Standard Time, sees a public holiday time as 9:00 AM - 6:00 PM." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:473 +msgid "" +":guilabel:`Working Hours`: If the holiday should only apply to employees who" +" have a specific set of working hours, select the working hours from the " +"drop-down menu. If left blank, the holiday applies to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:476 +msgid "" +":guilabel:`Work Entry Type`: If using the **Payroll** app, this field " +"defines how the :ref:`work entries ` for the holiday " +"appear. Select the work entry type from the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The list of public holidays in the configuration menu." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:484 +msgid "Mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:486 +msgid "" +"Some companies have special days where specific departments, or the entire " +"staff, is required to be present, and time off is not allowed on those " +"specific days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:489 +msgid "" +"These types of days are called *mandatory days* in Odoo. These can be " +"configured to be company-wide, or department specific. When configured, " +"employees in the specified department or company are unable to submit time " +"off requests for these mandatory days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:494 +msgid "Create mandatory days" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:496 +msgid "" +"No mandatory days are configured in Odoo by default. To create a mandatory " +"day, navigate to :menuselection:`Time Off app --> Configuration --> " +"Mandatory Days`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:499 +msgid "" +"Click the :guilabel:`New` button in the top-left corner, and a blank line " +"appears in the list." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:503 +msgid ":guilabel:`Name`: Enter the name of the mandatory day." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:504 +msgid "" +":guilabel:`Company`: If in a multi-company database, this field is visible, " +"and the current company populates this field, by default. Using the drop-" +"down menu, select the company the mandatory day is for." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:507 +msgid "" +":guilabel:`Departments`: This column is hidden by default. First, click the " +":icon:`oi-settings-adjust` :guilabel:`(additional options)` icon in the top-" +"right corner, next to :guilabel:`Color`, and then tick the checkbox next to " +":guilabel:`Departments` to reveal that column." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:512 +msgid "" +"Next, select the desired departments from the drop-down menu. Multiple " +"departments can be selected, and there is no limit to the amount of " +"departments that can be added." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:515 +msgid "" +"If this field is left blank, the mandatory day applies to the entire " +"company." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:516 +msgid "" +":guilabel:`Start Date`: Using the calendar picker, select the date the " +"mandatory day starts." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:517 +msgid "" +":guilabel:`End Date`: Using the calendar picker, select the date the " +"mandatory day ends. If creating a single mandatory day, the end date should " +"be the same as the start date." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:519 +msgid "" +":guilabel:`Color`: If desired, select a color from the available presented " +"options. If no color is desired, select the `No color` option, represented " +"by a white box with. The selected color appears on the main **Time Off** app" +" dashboard, in both the calendar and in the legend." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The Mandatory Days section with three configured days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:529 +msgid "" +"To view a color-coded schedule of the user's time off, and/or of the team " +"managed by them, navigate to :menuselection:`Time Off app --> Overview`. " +"This presents a calendar with the default filter of `My Team`, in a " +"quarterly (three month) view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:533 +msgid "" +"To change the time period displayed, click on the :icon:`fa-calendar` " +":guilabel:`(time period)` button to reveal a drop-down menu. Then, select " +"either :guilabel:`Today`, :guilabel:`This week`, :guilabel:`This month`, " +":guilabel:`This year`, or a custom time period, to present the calendar in " +"that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:538 +msgid "" +"To navigate forward or backward in time, in the selected increment " +"(:guilabel:`Month`, :guilabel:`Week`, etc.), click the :icon:`oi-arrow-left`" +" :guilabel:`(left arrow)` or :icon:`oi-arrow-right` :guilabel:`(right " +"arrow)` buttons to move either forward or backward in that specified amount " +"of time. For example, if :guilabel:`Month` is selected, the arrows adjust " +"the view by one month." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:544 +msgid "" +"To return to a view containing the current day, click the :icon:`fa-" +"crosshairs` :guilabel:`(Focus Today)` button at any time." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:547 +msgid "" +"Team members are listed alphabetically on individual lines, and their " +"requested time off, regardless of the status (*validated* or *to approve*), " +"is visible on the calendar." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:550 +msgid "" +"Each employee is color-coded. The employee's color is selected at random, " +"and does *not* correspond to the type of time off they requested." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:553 +msgid "" +"The status of the time off is represented by the color detail of the " +"request, either appearing solid (*validated*) or striped (*to approve*)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:556 +msgid "" +"The number of days or hours requested is written on the request (if there is" +" enough space)." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:558 +msgid "" +"At the bottom of the calendar, in the :guilabel:`Total` line, a bar graph " +"shows how many people are projected to be out on any given day. The number " +"on each individual bar represents the number of employees out for those " +"highlighted days." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:562 +msgid "" +"Click on a time off entry to view the details for the specific time off " +"entry. The total number of hours or days are listed, along with the start " +"and end time of the time off. To view the details of the time off request in" +" a modal, click the :guilabel:`View` button." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Overview of the user's team, with time off requests shown." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:574 +msgid "" +"The reporting feature allows users to view time off for their team, either " +"by employee or type of time off. This allows users to see which employees " +"are taking time off, how much time off they are taking, and what time off " +"types are being used." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:578 +msgid "" +"Any report can be added to a spreadsheet, when in either the :icon:`fa-area-" +"chart` :guilabel:`(Graph)` or :icon:`oi-view-pivot` :guilabel:`(Pivot)` " +"view, through the *Insert in Spreadsheet* button that appears in the top-" +"left of a report." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:583 +msgid "" +"If the **Documents** app is installed, an option to add the report to a " +"spreadsheet appears. If not, the report can be added to a *Dashboard*." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:587 +msgid "By employee" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:589 +msgid "" +"To view a list of employee time off requests, navigate to " +":menuselection:`Time Off app --> Reporting --> by Employee`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:592 +msgid "" +"The default report presents the current year's data in a list view, " +"displaying all the employees in alphabetical order. Each employee's line is " +"collapsed by default. To expand a line, click anywhere on the line." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:596 +msgid "" +"The view expands, and has the time off requests organized by time off type. " +"Click anywhere on a time off type line to expand it, and view all the " +"individual time off requests that fall under that type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:599 +msgid "" +"The information shown in the list includes: the :guilabel:`Employee` name, " +":guilabel:`Number of Days` off requested, the :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Status`, and :guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "Report of time off, shown by each employee in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:606 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"specific way. The various options are a :icon:`oi-view-list` " +":guilabel:`(List)`, or default view, :icon:`fa-area-chart` " +":guilabel:`(Graph)`, :icon:`oi-view-pivot` :guilabel:`(Pivot)` table, or " +":icon:`fa-calendar` :guilabel:`(Calendar)` view." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:611 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports and their" +" various options, refer to the :doc:`reporting <../essentials/reporting>` " +"documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:616 +msgid "By type" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:618 +msgid "" +"To view a graph of all time off, organized by time off type, navigate to " +":menuselection:`Time Off app --> Reporting --> by Type`. This shows all time" +" off requests in a default bar chart." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:621 +msgid "" +"Hover over a bar to view the :guilabel:`Duration (Days)` of that specific " +"time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "" +"The various time off types, and how many days requested, in a bar chart. Details are\n" +"highlighted in a red box." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:627 +msgid "" +"Click on a bar to go to a detailed list view of all the time off requests " +"for that time off type." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:629 +msgid "" +"Each request is listed, with the following information displayed: the " +":guilabel:`Employee`, :guilabel:`Number of Days`, :guilabel:`Request Type`, " +":guilabel:`Start Date`, :guilabel:`End Date`, :guilabel:`Status`, and the " +":guilabel:`Description`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:633 +msgid "" +"The report can be displayed in other ways, as well. Click the corresponding " +"button option in the top-right corner of the page to view the data in that " +"way. The various options are a :icon:`fa-area-chart` :guilabel:`(Graph)` " +"(the default view), :icon:`oi-view-list` :guilabel:`(List)`, or :icon:`oi-" +"view-pivot` :guilabel:`(Pivot)` table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:638 +msgid "" +"When a selection has been made, additional options appear for that " +"particular selection. For more detailed information on the reports, and " +"their various options, refer to the :doc:`reporting " +"<../essentials/reporting>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:643 +msgid "Balance" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:645 +msgid "" +"To view a pivot table of all time off balances, organized by time off type, " +"then further organized by how many days and hours are :guilabel:`Left` and " +":guilabel:`Planned`, navigate to :menuselection:`Time Off app --> Reporting " +"--> Balance`." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:649 +msgid "" +"This shows all time off balances in a default pivot table. The employees " +"populate the rows, while the various time off types and balances populate " +"the columns." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:-1 +msgid "The various time off balances, in a pivot table." +msgstr "" + +#: ../../content/applications/hr/time_off.rst:656 +msgid ":doc:`time_off/allocations`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:657 +msgid ":doc:`time_off/request_time_off`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:658 +msgid ":doc:`time_off/my_time`" +msgstr "" + +#: ../../content/applications/hr/time_off.rst:659 +msgid ":doc:`time_off/management`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:3 +msgid "Allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:5 +msgid "" +"Allocations are amounts of time off given to employees, either granted " +"immediately or earned as the employee works, through an accrual plan." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:8 +msgid "" +"Once :ref:`time off types ` and :ref:`accrual plans" +" ` have been configured, the next step is to " +"*allocate*, or give, time off to employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:12 +msgid "" +"The *Allocations* page of the **Time Off** app is **only** visible to users " +"who have either *Time Off Officer* or *Administrator* access rights for the " +"**Time Off** application. For more information on access rights, refer to " +"the :doc:`access rights <../../general/users/access_rights/>` documentation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:20 +msgid "Allocate time off" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:22 +msgid "" +"To create a new allocation, navigate to :menuselection:`Time Off app --> " +"Management --> Allocations`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:25 +msgid "" +"This presents a list of all current allocations, including their respective " +"statuses." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:27 +msgid "" +"Click :guilabel:`New` to allocate time off, and a blank " +":guilabel:`Allocation` form appears." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:29 +msgid "" +"After entering a name for the allocation on the first blank field of the " +"form, enter the following information:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:32 +msgid "" +":guilabel:`Name`: Enter a name for the allocation, typically containing the " +"type of time off, and the period of time it is available (example: `Annual " +"Vacation Time Off - 2025`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:34 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off that is being allocated to the employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:36 +msgid "" +":guilabel:`Allocation Type`: Select how the allocation is granted. Choose " +":guilabel:`Regular Allocation` if the time off is given immediately, or " +":guilabel:`Accrual Allocation` if the time off is earned through an " +":ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:39 +msgid "" +":guilabel:`Accrual Plan`: If :guilabel:`Accrual Allocation` is selected for " +"the :guilabel:`Allocation Type`, the :guilabel:`Accrual Plan` field appears." +" Using the drop-down menu, select the accrual plan associated with the " +"allocation. An accrual plan is **required** when using the " +":guilabel:`Accrual Allocation` type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:43 +msgid "" +":guilabel:`Validity Period/Start Date`: If :guilabel:`Regular Allocation` is" +" selected for the :guilabel:`Allocation Type`, this field is labeled " +":guilabel:`Validity Period`. If :guilabel:`Accrual Allocation` is selected " +"for the :guilabel:`Allocation Type`, this field is labeled :guilabel:`Start " +"Date`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:48 +msgid "" +"The current date populates the first date field, by default. To select " +"another date, click on the pre-populated date to reveal a popover calendar " +"window. Navigate to the desired start date for the allocation, and click on " +"the date to select it." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:52 +msgid "" +"If the allocation expires, select the expiration date in the next date " +"field. If the time off does *not* expire, leave the second date field blank." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:55 +msgid "" +"If :guilabel:`Accrual Allocation` is selected for the :guilabel:`Allocation " +"Type`, this second field is labeled :guilabel:`Run until`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:57 +msgid "" +":guilabel:`Allocation`: Enter the amount of time that is being allocated to " +"the employees. This field displays the time in either :guilabel:`Hours` or " +":guilabel:`Days`, depending on how the selected :ref:`Time Off Type " +"` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:60 +msgid "" +":guilabel:`Employee`: Using the drop-down menu, select the employee being " +"allocated the time off." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:61 +msgid "" +":guilabel:`Add a reason...`: If any description or note is necessary to " +"explain the time off allocation, enter it in this field at the bottom of the" +" form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"A new allocation form with all the fields filled out for the annual two week vacation\n" +"granted to all employees." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:69 +msgid "Accrual start date behavior" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:71 +msgid "" +"If the :guilabel:`Start Date` is in the middle of an accrual period, Odoo " +"adjusts it to the start or end of that period based on the *Accrued Gain " +"Time* entered on the :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:76 +msgid "" +"*At the start of the accrual period*: A :guilabel:`Start Date` of `06/16/25`" +" applies from `06/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:78 +msgid "" +"*At the end of the accrual period*: A :guilabel:`Start Date` of `06/18/25` " +"applies from `07/01/25`" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:81 +msgid "" +"Automatic adjustments on the start date to either the begining or end of an " +"accural period ensures accruals align with the defined period boundaries, " +"rather than the exact date entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:85 +msgid "Multiple requests" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:87 +msgid "" +"When allocating time off, it is common to allocate time to several employees" +" at once. This is done using the :guilabel:`Multiple Requests` feature." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:90 +msgid "" +"To allocate time to multiple employees in a single allocation, navigate to " +":menuselection:`Time Off app --> Management --> Allocations`. Then, click " +"the :icon:`fa-gear` :guilabel:`(Actions)` icon in the upper-left corner, " +"then click :icon:`fa-users` :guilabel:`Multiple Requests`. This reveals a " +":guilabel:`Multiple Requests` pop-up window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:95 +msgid "" +"This form is identical to the :ref:`Allocation form `, with an additional :guilabel:`Mode` field. The :guilabel:`Mode` " +"field determines how multiple employees are selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:98 +msgid "" +"Using the drop-down menu, select a :guilabel:`Mode` from one of the " +"following options:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:100 +msgid "" +":guilabel:`By Employee`: This option allows for the selection of multiple " +"individual employees that are unrelated in terms of department, company, or " +"tags. Selecting this reveals an :guilabel:`Employees` field. Select the " +"employees to receive the allocation in the :guilabel:`Employees` field. " +"There is no limit to the amount of employees that can be selected." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:104 +msgid "" +":guilabel:`By Company`: This option allows for the selection of all " +"employees within a specific company. Selecting this reveals a " +":guilabel:`Company` field. Select the :guilabel:`Company` to assign the " +"allocation to. Only one company can be assigned in the :guilabel:`Company` " +"field. When a company is selected, *all* employees within the company " +"receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:108 +msgid "" +":guilabel:`By Department`: This option allows for the selection of all " +"employees within a specific department. Selecting this reveals a " +":guilabel:`Department` field. Select the :guilabel:`Department` to assign " +"the allocation to. Only one department can be assigned in the " +":guilabel:`Department` field. When a department is selected, *all* employees" +" within the department receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:113 +msgid "" +":guilabel:`By Employee Tag`: This option allows for the selection of all " +"employees with a specific tag. Selecting this reveals an :guilabel:`Employee" +" Tag` field. Select the desired :guilabel:`Employee Tag` to select all " +"employees with that tag. Only one tag can be assigned in the " +":guilabel:`Employee Tag` field. When a tag is selected, *all* employees with" +" that tag receive the allocation." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:119 +msgid "" +"Next, select the :guilabel:`Time Off Type` using the drop-down menu. Once a " +":guilabel:`Time Off Type` is selected, the placeholder name, 'Allocation " +"Request', changes to the name of the selected :guilabel:`Time Off Type`, " +"including the amount of days. Change the name of the allocation, if desired." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:124 +msgid "" +"Fill out the remainder of the :ref:`Multiple Requests form " +"`, then click :guilabel:`Create Allocations` when " +"done." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:128 +msgid "" +"A company hosts an annual picnic, including a raffle. There are five raffle " +"prizes for a free vacation day, which must be redeemed by the end of the " +"year. The winners of this raffle all have the tag `Raffle Winner - 2025 " +"Employee Picnic Prize` added to their employee profiles." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:132 +msgid "" +"The time off officer creates multiple allocations, and configures the " +":ref:`Multiple Requests form ` as follows:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:135 +msgid "" +"The name for the allocation is :guilabel:`Vacation Day - Raffle Prize - 2025" +" Picnic`. The :guilabel:`Mode` is set to :guilabel:`By Employee Tag`, and " +"the :guilabel:`Tag` identified is :guilabel:`Raffle Winner - 2025 Employee " +"Picnic Prize`." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:139 +msgid "" +"The :guilabel:`Time Off Type` is set to :guilabel:`Vacation Time Off`, with " +"the :guilabel:`Allocation Type` set to :guilabel:`Regular Allocaiton`, since" +" the time off is given up front, and is not *earned*." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:143 +msgid "" +"The :guilabel:`Validity Period` is set to :guilabel:`07/18/2025` :icon:`oi-" +"arrow-right` :guilabel:`12/31/2025`, since the compnay picnic was that day, " +"and the earned vacation day expires at the end of the year." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:147 +msgid "" +"The :guilabel:`Allocation` is set to :guilabel:`1.00 Days`, and `A bonus " +"vacation day won at the annual Company Picnic.` appears in the details at " +"the bottom." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:0 +msgid "" +"An allocation request form filled out for a bonus vacation day for raffle " +"winners." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:156 +msgid "Request allocation" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:158 +msgid "" +"If an employee has used all their time off, or will run out of time off, " +"they can request an allocation for additional time. Allocations can be " +"requested in one of two ways, either from the :ref:`Dashboard " +"` or the :ref:`My Allocations `" +" view." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:162 +msgid "" +"To create a new allocation request, click either the :guilabel:`New " +"Allocation Request` button on the main **Time Off** dashboard, or the " +":guilabel:`New` button in the :guilabel:`My Allocations` list view. Both " +"buttons open a new allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:167 +msgid "" +"Both options open a new allocation request form, but when requested from the" +" :guilabel:`Dashboard`, the form appears in a pop-up window, and the " +"*Validity Period* field does **not** appear." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:171 +msgid "" +"When requested from the :guilabel:`My Allocations` list view, the screen " +"navigates to a new allocation request page, instead of presenting a pop-up " +"window." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:174 +msgid "Enter the following information on the new allocation request form:" +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:176 +msgid "" +":guilabel:`Time Off Type`: Using the drop-down menu, select the type of time" +" off being requested for the allocation. After a selection is made, the " +"title updates with the time off type." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:178 +msgid "" +":guilabel:`Validity Period`: By default, the current date populates this " +"field, and it is **not** able to be modified. This field **only** appears " +"when requesting an allocation from the :guilabel:`My Allocations` view " +"(:menuselection:`Time Off --> My Time --> My Allocations`)." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:181 +msgid "" +":guilabel:`Allocation`: Enter the amount of time being requested in this " +"field. The format is presented in either :guilabel:`Days` or " +":guilabel:`Hours`, depending on how the :guilabel:`Time Off Type` is " +"configured. Once this field is populated, the name of the allocation request" +" is updated to include the amount of time being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:185 +msgid "" +":guilabel:`Add a reason...`: Enter a description for the allocation request " +"in this field. This should include any details that approvers may need to " +"approve the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:188 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button on the :guilabel:`New Allocation` pop-up " +"window to save the information and submit the request." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:191 +msgid "" +"If the form was completed from the :guilabel:`My Allocations` list view, the" +" information is automatically saved as it is entered." +msgstr "" + +#: ../../content/applications/hr/time_off/allocations.rst:-1 +msgid "" +"An allocation request form filled out for an employee requesting an additional week of\n" +"sick time." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:3 +msgid "Management" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:7 +msgid "" +"Time off and allocation requests undergo an approval process before being " +"granted. Requests either need one or two approvals, if any, depending on how" +" the specific type of time off is configured. All these configurations can " +"be found under the *Management* section of the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:11 +msgid "" +"Only users who can :ref:`approve allocation and time off requests " +"` see the :guilabel:`Management` section in the " +"**Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:17 +msgid "Manage time off" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:19 +msgid "" +"To view time off requests that need approval, navigate to " +":menuselection:`Time Off app --> Management --> Time Off`. Doing so reveals " +"the :guilabel:`All Time Off` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:22 +msgid "" +"The only time off requests that are visible on this page belong to employees" +" the user either has :guilabel:`Time Off Officer` or " +":guilabel:`Administrator` access rights for in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:26 +msgid "" +"The default filter on the :guilabel:`All Time Off` page is :icon:`fa-filter`" +" :guilabel:`Waiting For Me`. This filter only presents time off requests " +"that need to be approved for current employees on the user's team, with a " +"status of either :guilabel:`To Approve` or :guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:30 +msgid "" +"On the left side of the :guilabel:`All Time Off` page, there are various " +"grouping options that can be used to narrow down the presented time off " +"requests, located beneath the :guilabel:`Status` and :guilabel:`Department` " +"headings." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:34 +msgid "" +"Since only time off requests that need to be approved are shown, the only " +":guilabel:`Status` options are :guilabel:`All`, :guilabel:`To Approve`, and " +":guilabel:`Second Approval`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:37 +msgid "" +"The various departments the user is a member of, and manages employees " +"under, also appear on the left side of the page, under " +":guilabel:`Departments`." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:41 +msgid "" +"If no requests fall under one of the status options or departments, that " +"status or department is **not** visible on the left-side menu." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:44 +msgid "" +"To only display time off requests for specific departments, click on the " +":guilabel:`Department` on the left-hand side of the page. Only requests " +"within the selected department are then presented." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:47 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:50 +msgid "" +"The :guilabel:`To Approve` and :guilabel:`Second Approval` requests are " +"highlighted in yellow, and are the only ones that appear in the list by " +"default." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:53 +msgid "" +"If the :icon:`fa-filter` :guilabel:`Waiting For Me` filter is removed, all " +"statuses appear." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:55 +msgid "" +":guilabel:`Approved` requests are highlighted in green, :guilabel:`To " +"Submit` (drafts) requests are highlighted in blue, and the " +":guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:58 +msgid "" +"To approve a time off request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:61 +msgid "" +"To validate a time off request that has already been approved, and is " +"waiting on a second approval, click the :icon:`fa-check` " +":guilabel:`Validate` button at the end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:64 +msgid "" +"To refuse a request, click the :icon:`fa-times` :guilabel:`Refuse` button at" +" the far end of the line." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Time off requests with the filter, groupings, and status sections " +"highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:70 +msgid "" +"For more details, click anywhere on the time off request line (except for " +"the :icon:`fa-thumbs-up` :guilabel:`Approve`, :icon:`fa-check` " +":guilabel:`Validate` icon, and :icon:`fa-times` :guilabel:`Refuse` buttons)." +" Doing so loads that specific time off request form. Depending on the rights" +" of the user, changes can be made." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:75 +msgid "" +"To modify the request, make any desired changes to the form. All changes are" +" automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:77 +msgid "" +"It is also possible to approve, validate, or refuse the request from this " +"form. Click the :guilabel:`Approve` button to approve, the " +":guilabel:`Validate` button to validate, or the :guilabel:`Refuse` button to" +" refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:84 +msgid "Manage allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:86 +msgid "" +"To view allocations that need approval, navigate to :menuselection:`Time Off" +" app --> Management --> Allocations`. Doing so reveals the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:89 +msgid "" +"The user is only presented with allocations for employees they have either " +":guilabel:`Time Off Officer` or :guilabel:`Administrator` access rights for " +"in the **Time Off** application." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:92 +msgid "" +"The default filters configured on the :guilabel:`Allocations` page are " +":guilabel:`First Approval` and :guilabel:`My Team`. These default filters " +"only present employees that the user manages and are awaiting their first " +"approval. Approved and refused allocation requests are not shown." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:96 +msgid "" +"The left side of the :guilabel:`Allocations` page has various grouping " +"options to narrow down the presented allocation requests." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:99 +msgid "" +"The :guilabel:`Status` options are: :guilabel:`All`, :guilabel:`To Approve`," +" :guilabel:`Refused`, and :guilabel:`Approved`. Click on a specific " +":guilabel:`Status` to view only requests with that specific status." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:103 +msgid "" +"To view all allocation requests, regardless of status, click :guilabel:`All`" +" under the :guilabel:`Status` heading." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:106 +msgid "" +"It is also possible to display allocation requests by department. Click on " +"the desired :guilabel:`Department` on the left side of the " +":guilabel:`Allocations` page, to only present allocations for that specific " +"department." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:111 +msgid "" +"The groupings on the left side **only** present allocation requests that " +"fall under the default filters of :guilabel:`My Team` and :guilabel:`Active " +"Employee`, if those default filters are not removed from the " +":guilabel:`Search...` bar. Only the statuses for allocation requests that " +"fall under those filters are presented on the left side." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:116 +msgid "" +"For example, if there are no requests with a status of :guilabel:`To " +"Submit`, that status option does not appear in the left-hand side of the " +":guilabel:`Allocations` page." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:119 +msgid "" +"All departments for the user's employees appear in the list. If there are no" +" allocation requests that fall under that department matching the " +"preconfigured filters, the list is blank." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:122 +msgid "" +"It is always possible to remove any of the preconfigured filters, by " +"clicking the :icon:`fa-times` :guilabel:`(remove)` icon on the specific " +"filter to remove it." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:125 +msgid "" +"The status column displays the status of each request, with the status " +"highlighted in a specific color. The :guilabel:`To Approve` requests are " +"highlighted in yellow, and if the default :guilabel:`First Approval` filter " +"is removed, the :guilabel:`Approved` requests are highlighted in green, and " +"the :guilabel:`Refused` requests are highlighted in gray." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:130 +msgid "" +"To approve an allocation request, click the :icon:`fa-thumbs-up` " +":guilabel:`Approve` button at the end of the line. To refuse a request, " +"click the :icon:`fa-times` :guilabel:`Refuse` button." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:-1 +msgid "" +"Allocations with the filter, groupings, and status sections highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:136 +msgid "" +"If more details are needed, click anywhere on the allocation request line " +"(except for the :icon:`fa-thumbs-up` :guilabel:`Approve` or :icon:`fa-times`" +" :guilabel:`Refuse` buttons) to view the specific request in detail, via the" +" allocation request form." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:140 +msgid "" +"Depending on the rights of the user, changes can be made to the allocation " +"request form that appears. To modify the request, make any desired changes " +"to the form. All changes are automatically saved." +msgstr "" + +#: ../../content/applications/hr/time_off/management.rst:144 +msgid "" +"It is also possible to approve or refuse the request from this form. Click " +"the :guilabel:`Approve` button to approve, or the :guilabel:`Refuse` button " +"to refuse the request." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:3 +msgid "My time" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:5 +msgid "" +"The *My Time* menu of the **Time Off** app houses all the various time off " +"information for the signed-in user." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:8 +msgid "" +"This includes the main **Time Off** :ref:`dashboard `, " +"which displays an overview of the various time off balances, as well as " +":ref:`time-off requests ` and :ref:`allocations " +"`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:15 +msgid "Dashboard" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:17 +msgid "" +"All users have access to the **Time Off** :guilabel:`Dashboard`, which is " +"the first page that appears when the **Time Off** app is opened. The " +":guilabel:`Dashboard` can also be accessed at any point in the application, " +"by navigating to :menuselection:`Time Off app --> My Time --> Dashboard`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:21 +msgid "" +"The dashboard shows a summary of the user's time off, and the entire current" +" year, with the current day highlighted in a red circle." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:24 +msgid "" +"To change the view, click on the :guilabel:`Year` button to reveal a drop-" +"down menu. Then, select either :guilabel:`Day`, :guilabel:`Week`, or " +":guilabel:`Month` to present the calendar in that corresponding view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:29 +msgid "" +"To change the displayed dates, click the :icon:`fa-arrow-left` " +":guilabel:`(left arrow)` or :icon:`fa-arrow-right` :guilabel:`(right arrow)`" +" icons to the left of the :guilabel:`Year` button. The calendar view adjusts" +" in increments of the selected view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:33 +msgid "" +"For example, if :guilabel:`Year` is selected, the arrows adjust the view by " +"one year." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:35 +msgid "" +"To reset the view, so it includes the current date, click the " +":guilabel:`Today` button." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:37 +msgid "" +"Above the calendar view is a summary of the user's time off balances. Every " +"time off type that has been allocated appears in its own summary box. Each " +"summary lists the type of time off, the corresponding icon, the current " +"available balance (in hours or days), and an expiration date (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:42 +msgid "" +"To view the full details of a time off balance, click the :icon:`fa-" +"question-circle-o` :guilabel:`(question mark)` icon at the end of the " +":guilabel:`(DAYS/HOURS) AVAILABLE` on the time off summary. The complete " +"details are presented in a popover window, including the " +":guilabel:`Allocated` time, :guilabel:`Accrual (Future)` time, " +":guilabel:`Approved` time off scheduled, :guilabel:`Planned` time off, and " +"the currently :guilabel:`Available` time off." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "A view of the complete time off balance details in the popover window." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:51 +msgid "" +"A user can also select a future date to see an estimate of how much time " +"they should accrue by that point. On the right side of the time off summary " +"blocks, there is a :guilabel:`Balance at the (date)` field. Click on the " +"date, and a calendar selector popover appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:56 +msgid "" +"The :guilabel:`Balance at the (date)` field **only** appears if the user is " +"accruing time off through an :ref:`accrual plan `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:59 +msgid "" +"The current date is the default date selected. Navigate to the desired date," +" and Odoo displays the time off balances the user should have on that date. " +"This takes into account all time off currently planned and approved. To " +"return to the current date, click the :guilabel:`Today` button to the right " +"of the date field." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:64 +msgid "" +"On the right side of the calendar, the various time off types are displayed," +" each with their own corresponding color. The :guilabel:`Legend` explains " +"how the various statuses for time off requests are presented." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:68 +msgid "" +"Time off that has been validated appears in a solid color. Time off requests" +" that still are still in the :guilabel:`To Approve` stage, appear with white" +" stripes in the color. :guilabel:`Refused` time off requests have a line " +"through the dates." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:72 +msgid "" +"The color for each request corresponds to the specified color set with the " +"various time off types, listed in the section above the :guilabel:`Legend`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:75 +msgid "" +"New time off requests can be made from the :guilabel:`Dashboard`. Click the " +":guilabel:`New` button in the upper-left corner, and a :doc:`New Time Off " +"` pop-up window appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:78 +msgid "" +"New allocation requests can also be made from the :guilabel:`Dashboard`. " +"Click the :guilabel:`New Allocation Request` button to request more time " +"off, and a :ref:`New Allocation ` pop-up window" +" appears." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "" +"Time off dashboard view with the legend, time off summaries, and view " +"buttons highlighted." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:88 +msgid "My time off" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:90 +msgid "" +"To view a list of all the signed-in user's time off requests, navigate to " +":menuselection:`Time Off app --> My Time --> My Time Off`. Here, all time " +"off requests, both past and present, appear in a list view, grouped by " +"month." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:94 +msgid "" +"The list includes the following information for each request: the " +":guilabel:`Time Off Type`, :guilabel:`Description`, :guilabel:`Start Date`, " +":guilabel:`End Date`, :guilabel:`Duration`, and :guilabel:`Status`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:98 +msgid "" +"A new time off request can be made from this view. Click the :guilabel:`New`" +" button to :doc:`request_time_off`." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Time list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:107 +msgid "My allocations" +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:109 +msgid "" +"To view a list of all allocations, navigate to :menuselection:`Time Off app " +"--> My Time --> My Allocations`. All allocations and requested allocations " +"appear in a list view." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:112 +msgid "" +"The information presented on the :guilabel:`My Allocations` page includes: " +":guilabel:`Time Off Type`, :guilabel:`Amount`, :guilabel:`Allocation Type`, " +":guilabel:`Accrual Plan`, and :guilabel:`Status`. If the signed-in user has " +"the appropriate access rights, they may also see an option to " +":guilabel:`Approve` requests, if applicable." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:117 +msgid "" +"A new allocation request can be made from this view, as well. Click the " +":guilabel:`New` button to :ref:`request an allocation `." +msgstr "" + +#: ../../content/applications/hr/time_off/my_time.rst:-1 +msgid "My Allocations list view with all requests." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:3 +msgid "Request time off" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:5 +msgid "" +"Once time off has been allocated to an employee, a request to use it can be " +"submitted." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:7 +msgid "" +"Time off can be requested in one of two ways: either from the main *Time " +"Off* application :guilabel:`Dashboard` (:menuselection:`Time Off app --> My " +"Time --> Dashboard`), or from the :guilabel:`My Time Off` dashboard view " +"(:menuselection:`Time Off app --> My Time --> My Time Off`)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:11 +msgid "" +"To create a new request for time off, click the :guilabel:`New` button on " +"either the main *Time Off* :guilabel:`Dashboard` or the :guilabel:`My Time " +"Off` dashboard, in the default list view." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:15 +msgid "" +"Both :guilabel:`New` buttons allow the user to request time off, but when " +"requested from the :guilabel:`Dashboard`, a :guilabel:`New Time Off` request" +" form appears in a pop-up window. When requested from the :guilabel:`My Time" +" Off` list view, the screen navigates to a new time off request page, " +"instead." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:20 +msgid "" +"Enter the following information on the :guilabel:`New Time Off` request " +"form:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:22 +msgid "" +":guilabel:`Time Off Type`: select the type of time off being requested from " +"the drop-down menu." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:23 +msgid "" +":guilabel:`Dates`: enter the dates that the time off falls under. There are " +"two fields to populate: the start and end dates. Click on either date field " +"and a popover calendar appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:26 +msgid "" +"Click on the start date, then click on the end date. The selected start and " +"end dates are circled, and the dates between them are highlighted (if " +"applicable)." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:29 +msgid "" +"If only requesting time off for a single day, click on the start date, then " +"click the same date again for the end date." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:32 +msgid "" +"When the correct dates are selected, click the :guilabel:`Apply` button." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:34 +msgid "" +"The selected dates now populate the two portions of the :guilabel:`Dates` " +"field." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:36 +msgid "" +"If the selected :guilabel:`Time Off Type` is configured to have the time off" +" taken in hours, the following two fields also appear:" +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:39 +msgid "" +":guilabel:`Half Day`: if the time off request is for a half day, tick this " +"checkbox. When this is selected, the second date field disappears, and is " +"replaced with a drop-down menu. From that drop-down menu, select either " +":guilabel:`Morning` or :guilabel:`Afternoon` to indicate which half of the " +"day is being requested." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:43 +msgid "" +":guilabel:`Custom Hours`: if the time off requested is not a whole or half " +"day, tick this checkbox. If selected, a :guilabel:`From` and :guilabel:`To` " +"field appears beneath this option. Using the drop-down menu, select the " +"start and end time for the time off request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:47 +msgid "" +":guilabel:`Duration`: this field updates automatically once the " +":guilabel:`Date` section is completed. If the :guilabel:`Date` section is " +"modified, this section automatically updates to reflect the total time off " +"requested. This field is in either hours or days, depending on how the " +"selected :guilabel:`Time Off Type` is configured." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:51 +msgid "" +":guilabel:`Description`: enter a description for the time off request. This " +"should include any details that managers and approvers may need to approve " +"the request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:53 +msgid "" +":guilabel:`Supporting Document`: this field only appears if the " +":guilabel:`Time Off Type` selected allows for the attachment of documents. " +"Click the :guilabel:`Attach File` button, and a file explorer window " +"appears." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:57 +msgid "" +"Navigate to the desired files that should be attached, select them, then " +"click The :guilabel:`Open` button. The files then appear on the time off " +"request form. Multiple documents can be attached, if necessary." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:61 +msgid "" +"If the request was created from the :guilabel:`Dashboard`, click the " +":guilabel:`Save & Close` button to save the information, and submit the " +"request." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:64 +msgid "" +"If the form was completed from the :guilabel:`My Time Off` list view, the " +"information is automatically saved as it is entered. However, the form can " +"be saved manually at any time by clicking the :icon:`fa-cloud-upload` " +":guilabel:`(cloud upload)` icon." +msgstr "" + +#: ../../content/applications/hr/time_off/request_time_off.rst:-1 +msgid "" +"A time off request form filled out for an employee home sick for two days " +"with the flu." +msgstr "" diff --git a/locale/zh_CN/LC_MESSAGES/studio.po b/locale/zh_CN/LC_MESSAGES/studio.po new file mode 100644 index 0000000000..fbe023df5f --- /dev/null +++ b/locale/zh_CN/LC_MESSAGES/studio.po @@ -0,0 +1,4257 @@ +# SOME DESCRIPTIVE TITLE. +# Copyright (C) Odoo S.A. +# This file is distributed under the same license as the Odoo package. +# FIRST AUTHOR , YEAR. +# +#, fuzzy +msgid "" +msgstr "" +"Project-Id-Version: Odoo 18.0\n" +"Report-Msgid-Bugs-To: \n" +"POT-Creation-Date: 2025-08-18 08:33+0000\n" +"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" +"Last-Translator: FULL NAME \n" +"Language-Team: LANGUAGE \n" +"MIME-Version: 1.0\n" +"Content-Type: text/plain; charset=UTF-8\n" +"Content-Transfer-Encoding: 8bit\n" + +#: ../../content/applications/studio.rst:6 +msgid "Studio" +msgstr "" + +#: ../../content/applications/studio.rst:18 +msgid "" +"**Odoo Studio** is a toolbox used to customize Odoo without coding " +"knowledge. For example, in any app, add or modify:" +msgstr "" + +#: ../../content/applications/studio.rst:21 +msgid ":doc:`Fields `" +msgstr "" + +#: ../../content/applications/studio.rst:22 +msgid ":doc:`Views `" +msgstr "" + +#: ../../content/applications/studio.rst:23 +msgid ":doc:`Models `" +msgstr "" + +#: ../../content/applications/studio.rst:24 +msgid ":doc:`Automation rules `" +msgstr "" + +#: ../../content/applications/studio.rst:25 +msgid ":doc:`Webhooks `" +msgstr "" + +#: ../../content/applications/studio.rst:26 +msgid ":doc:`PDF reports `" +msgstr "" + +#: ../../content/applications/studio.rst:27 +msgid ":doc:`Approval rules `" +msgstr "" + +#: ../../content/applications/studio.rst:28 +msgid "Security rules" +msgstr "" + +#: ../../content/applications/studio.rst:30 +msgid "" +"Learn how to :doc:`build an app from scratch `." +msgstr "" + +#: ../../content/applications/studio.rst:34 +msgid "" +"To access **Studio**, navigate to the app and model you want to modify, then" +" click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) icon. " +"Alternatively, with any app open, click the :icon:`oi-studio` " +"(:guilabel:`Toggle Studio`) icon and navigate to the relevant app and model." +msgstr "" + +#: ../../content/applications/studio.rst:38 +msgid "" +"To close **Studio**, click :guilabel:`Close` in the upper-right corner." +msgstr "" + +#: ../../content/applications/studio.rst:41 +msgid "" +"Installing **Studio** in an Odoo database on the *Standard* pricing plan " +"automatically triggers an upsell to the *Custom* pricing plan." +msgstr "" + +#: ../../content/applications/studio.rst:44 +msgid "" +"**For yearly or multi-year contracts**: An upsell order is created with a " +"30-day limit." +msgstr "" + +#: ../../content/applications/studio.rst:45 +msgid "" +"**For monthly contracts**: The subscription automatically switches to the " +"*Custom* plan and the new rate is applied when the next bill is generated." +msgstr "" + +#: ../../content/applications/studio.rst:48 +msgid "" +"For more information, refer to `Odoo's pricing page " +"`_ or contact your account manager." +msgstr "" + +#: ../../content/applications/studio.rst:52 +msgid "`Odoo Tutorials: Studio `_" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:3 +msgid "Approval rules" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:5 +msgid "" +"Approval rules are used to automate approval processes for actions. They " +"allow you to define the criteria for when an approval is required before an " +"action can be performed using a button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:9 +msgid "Configuration" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:11 +msgid "To add approval rules with Studio, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:13 +msgid "" +":ref:`Open Studio ` and switch to the required :doc:`view " +"`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:14 +msgid "Select the button to which the rule should be applied." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:15 +msgid "" +"Click :icon:`fa-plus` :guilabel:`Add an approval step` in the :icon:`fa-" +"server` :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:17 +msgid "" +"Specify which users are responsible for approving the action by using one of" +" the following fields or both:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:20 +msgid ":guilabel:`Approvers` to specify one or several users;" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:21 +msgid ":guilabel:`Approver Group` to specify one user group." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:24 +msgid "" +"An activity is created for all users set as :guilabel:`Approvers` when their" +" approval is requested." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:27 +msgid "" +"(*optional*) Select the :guilabel:`Users to Notify` via an internal note " +"when the action is approved or rejected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:29 +msgid "" +"(*optional*) Add a :guilabel:`Description` to be displayed on the button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:32 +msgid "" +"You can specify under which condition(s) an approval step should be applied " +"by clicking the :icon:`fa-filter` (:guilabel:`filter`) icon next to the " +":guilabel:`Approvers` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:35 +msgid "" +"To add another approval step, click :icon:`fa-plus` :guilabel:`Add an " +"approval step`. When there are multiple steps, you can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:38 +msgid "" +"Enable :guilabel:`Exclusive Approval` on any step so that a user who " +"approves a step cannot approve another step for the same record." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:40 +msgid "" +"Change the :guilabel:`Approval Order` of the steps by selecting a number, " +"`1` being the first step, `2` the second step, and so on. A user responsible" +" for a higher step can approve/reject previous step(s) unless " +":guilabel:`Exclusive Approval` is selected." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:44 +msgid "" +"Click the :icon:`fa-trash` (:guilabel:`trash`) icon next to the " +":guilabel:`Approvers` field to remove an approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:48 +msgid "" +"You can create :ref:`user groups ` specifically for " +"approvals." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:53 +msgid "Use" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:55 +msgid "" +"Once an approval rule has been defined for a button, a **user avatar** icon " +"is displayed next to the button's label for each approval step. Clicking an " +"icon reveals the step(s)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:-1 +msgid "Confirm button with two approval steps" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:62 +msgid "" +"If an unauthorized user clicks the button, an error message is displayed and" +" an activity is created for the users specified in the :guilabel:`Approvers`" +" field, if any." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:65 +msgid "Authorized users can:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:67 +msgid "" +"Perform the action directly by clicking the button if it is the last/only " +"approval step." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:68 +msgid "" +"Approve the action and let another user perform it - or move it to the next " +"approval step - by clicking the **user avatar** icon next to the button's " +"label, then clicking the :icon:`fa-check` (:guilabel:`approve`)." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:71 +msgid "" +"Reject the action by clicking the **user avatar** icon next to the button's " +"label and then the :icon:`fa-times` (:guilabel:`reject`) button." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:73 +msgid "" +"(only for users selected under the :guilabel:`Approvers` field) Delegate " +"their approval rights to one or several users for **all records** by:" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:76 +msgid "" +"Clicking the :icon:`oi-view-kanban` (:guilabel:`kanban view`) icon and then " +":guilabel:`Delegate`." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:78 +msgid "" +"Selecting one or several :guilabel:`Approvers`, :guilabel:`Until` when they " +"will have approval rights (forever if left empty), and, optionally, the " +"user(s) who should be notified via an internal note using the " +":guilabel:`Notify to` field." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:0 +msgid "Delegate to dialog" +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:86 +msgid "" +"A user who approves/rejects an action can revoke their decision by clicking " +"the **user avatar** icon next to the button's label and then the :icon:`fa-" +"undo` (:guilabel:`revoke`) button. They can also revoke the decision of " +"other users for steps with a lower :guilabel:`Approval Order` unless " +":guilabel:`Exclusive Approval` is enabled." +msgstr "" + +#: ../../content/applications/studio/approval_rules.rst:90 +msgid "" +"Approvals are tracked in the record's chatter. An approval entry is also " +"created every time a Studio approval-related action is performed. To access " +"approval entries, :doc:`activate the developer mode " +"` and go to :menuselection:`Settings " +"--> Technical --> Studio Approval Entries`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:5 +msgid "Automation rules" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:7 +msgid "" +"Automation rules allow the execution of one or more predefined actions in " +"response to a specific trigger, e.g., create an activity when a field is set" +" to a specific value, or archive a record 7 days after its last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:11 +msgid "" +"When creating an automation rule, :ref:`domain filters ` allow you to add conditions that must be met for the " +"automation rule to run, e.g., the opportunity must be assigned to a specific" +" salesperson, or the state of the record must not be :guilabel:`Draft`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:16 +msgid "To create an automation rule with **Odoo Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:18 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Automations`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:19 +msgid "" +"Give the automation rule a clear, meaningful name that identifies its " +"purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:20 +msgid "" +"Select the :ref:`trigger ` and, if " +"necessary, fill in the fields that appear on the screen based on the chosen " +"trigger." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:22 +msgid "" +"Click :guilabel:`Add an action`, then select the :guilabel:`Type` of " +":ref:`action ` and fill in the fields that " +"appear on the screen based on your selected action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:25 +msgid "Click :guilabel:`Save & Close` or :guilabel:`Save & New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:29 +msgid "" +"To ensure follow-up on less satisfied clients, this automation rule creates " +"an activity 3 months after a sales order is created for clients with a " +"satisfaction percentage lower than 30%." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an automation rule on the Subscription model" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:37 +msgid "" +"Use the :guilabel:`Notes` tab to document the purpose and functioning of " +"automation rules. This makes rules easier to maintain and facilitates " +"collaboration between users." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:39 +msgid "" +"To modify the :doc:`model ` targeted by the automation " +"rule, switch models before clicking :guilabel:`Automations` in Studio, or " +":ref:`activate developer mode `, create or edit an " +"automation rule, and select the :guilabel:`Model` in the " +":guilabel:`Automation Rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:43 +msgid "" +"Automation rules can be created from any kanban stage by clicking the " +":icon:`fa-cog` :guilabel:`(Settings)` icon that appears when hovering over " +"the kanban stage name, then selecting :guilabel:`Automations`. In this case," +" the :guilabel:`Trigger` is set to :guilabel:`Stage is set to` by default, " +"but it can be changed if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Create automations from a kanban stage" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:54 +msgid "Trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:56 +msgid "" +"The :guilabel:`Trigger` is used to define what kind of event needs to occur " +"for the automation rule to run. The available triggers depend on the " +":doc:`model `. Five trigger categories are available " +"overall:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:60 +msgid ":ref:`studio/automated-actions/trigger-values-updated`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:61 +msgid ":ref:`studio/automated-actions/trigger-email-events`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:62 +msgid ":ref:`studio/automated-actions/trigger-timing-conditions`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:63 +msgid ":ref:`studio/automated-actions/trigger-custom`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:64 +msgid ":ref:`studio/automated-actions/trigger-external`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:69 +msgid "Adding conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:71 +msgid "" +"Domain filters allow you to determine the records an automation rule should " +"target or exclude. Efficient filtering enhances overall performance as it " +"avoids unnecessary processing on records that are not impacted by the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:76 +msgid "" +":ref:`Activate developer mode ` before creating an " +"automation rule to have the most flexibility in adding domain filters." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:79 +msgid "" +"Depending on the trigger chosen, it is possible to define one or more " +"conditions a record must meet *before* and/or *after* a trigger occurs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:82 +msgid "" +"The :guilabel:`Before Update Domain` defines the conditions a record must " +"meet *before* the trigger event occurs, e.g., the record must have `Type = " +"Customer Invoice` and `Status = Posted`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:85 +msgid "" +"With :ref:`developer mode activated `, click :guilabel:`Edit" +" Domain`, if available, then :guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:88 +msgid "" +":guilabel:`Extra Conditions`, or in some cases :guilabel:`Apply on` filters," +" define the conditions a record must meet *after* the trigger event occurs, " +"e.g., the customer invoice must have `Payment Status = Partially Paid`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:92 +msgid "" +"With :ref:`developer mode activated ` if needed, click " +":guilabel:`Add conditions` or :guilabel:`Edit Domain`, as relevant, then " +":guilabel:`New Rule`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:95 +msgid "" +"When a :ref:`trigger ` occurs, e.g., the " +"payment status of a posted customer invoice is updated, the automation rule " +"checks the defined conditions and only executes the :ref:`action " +"` if the record matches those conditions." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:100 +msgid "" +"If the automated action should be executed when an email address is set for " +"the first time (in contrast to modifying an email address) on an existing " +"contact that is an individual rather than a company, use `Email is not set` " +"and `Is a Company is not set` as the :guilabel:`Before Update Domain` and " +"`Email is set` as the :guilabel:`Apply on` domain." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a trigger with a Before Update Domain" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:109 +msgid "" +"The :guilabel:`Before Update Domain` is not checked upon the creation of a " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:114 +msgid "Values Updated" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:116 +msgid "" +"Trigger automated actions when specific changes happen in the database. The " +"triggers available in this category depend on the model and are based on " +"common changes, such as adding a specific tag (e.g., to a task) or setting a" +" field's value (e.g., setting the :guilabel:`User` field)." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:120 +msgid "Select the trigger, then select a value if required." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:125 +msgid "Email Events" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:127 +msgid "Trigger automated actions upon receiving or sending emails." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:132 +msgid "Timing Conditions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:134 +msgid "" +"Trigger automated actions at a point in time relative to a date field or to " +"the creation or update of a record. The following triggers are available:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:137 +msgid "" +":guilabel:`Based on date field`: The action is triggered a defined period of" +" time before or after the date of the selected date field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:139 +msgid "" +":guilabel:`After creation`: The action is triggered a defined period of time" +" after a record is created and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:141 +msgid "" +":guilabel:`After last update`: The action is triggered a defined period of " +"time after an existing record is edited and saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:144 +msgid "You can then define:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:146 +msgid "" +"a :guilabel:`Delay`: Specify the number of minutes, hours, days, or months. " +"To have an action executed before the trigger date, specify a negative " +"number. If you selected the :guilabel:`Based on date field` trigger, you " +"must also select the date field to be used to determine the delay." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:151 +msgid "" +"By default, the scheduler checks for time-triggered automation rules every " +"240 minutes, or 4 hours. This frequency is generally sufficient for delays " +"such as 3 months after the order date or 7 days after the last update." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:155 +msgid "" +"For delays of less than the equivalent of 2400 minutes, or 40 hours, the " +"system recalculates the frequency of this check to ensure that more granular" +" delays, e.g., 1 hour before the event start date and time, or 30 minutes " +"after creation, can be respected as closely as possible." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:159 +msgid "" +"An on-screen message indicates the possible delay after the scheduled " +"triggering of the rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Message about possible delay after scheduled execution" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:164 +msgid "" +"To view or manually edit the frequency of the scheduler, with " +":ref:`developer mode activated `, go to " +":menuselection:`Settings --> Technical --> Scheduled Actions` to see all " +"scheduled actions for your database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:168 +msgid "" +"Enter `Automation` in the search bar, then, in the list of results, click " +":guilabel:`Automation Rules: check and execute`. If desired, update the " +"value of the :guilabel:`Execute Every` field. Click :guilabel:`Run Manually`" +" at any time to manually trigger this scheduled action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:172 +msgid "" +":guilabel:`Extra Conditions`: Click :guilabel:`Add condition`, then specify " +"the conditions to be met for the automation rule to run. Click " +":guilabel:`New Rule` to add another condition." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:175 +msgid "" +"The action is executed when the delay is reached and the conditions are met." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:178 +msgid "" +"To send a reminder email 30 minutes *before* the start of a calendar event, " +"select :guilabel:`Start (Calendar Event)` as the date field for the " +":guilabel:`Trigger` and set the :guilabel:`Delay` to `-30` " +":guilabel:`Minutes`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +#: ../../content/applications/studio/automated_actions.rst:-1 +msgid "Example of a Based on date field trigger" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:188 +msgid "Custom" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:190 +msgid "Trigger automated actions:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:192 +msgid ":guilabel:`On save`: when a record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:193 +msgid ":guilabel:`On deletion`: when a record is deleted." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:194 +msgid "" +":guilabel:`On UI change`: when a field's value is changed on the :ref:`Form " +"view `, even before the record is saved." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:197 +msgid "" +"For the :guilabel:`On save` and :guilabel:`On UI change` triggers, you " +"**must** then select the field(s) to be used to trigger the automation rule " +"in the :guilabel:`When updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:201 +msgid "" +"If no field is selected in the :guilabel:`When updating` field, the " +"automated action may be executed multiple times per record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:204 +msgid "" +"Optionally, you can also define additional conditions to be met to trigger " +"the automation rule in the :guilabel:`Apply on` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:208 +msgid "" +"To trigger an automated action *upon* the creation of a record, e.g., when a" +" new contact is created, select the :ref:`On save ` trigger and use `ID is not set` as the " +":guilabel:`Before Update Domain` and `ID is set` as the :guilabel:`Apply on`" +" domain. Make sure the correct field is selected in the :guilabel:`When " +"updating` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:214 +msgid "" +"When a new contact is saved, it is automatically assigned a database ID, " +"thereby triggering the automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a triggering an action upon creation of a record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:221 +msgid "" +"The :guilabel:`On UI change` trigger can only be used with the :ref:`Execute" +" Code ` action and only works " +"when a modification is made manually. The action is not executed if the " +"field is changed through another automation rule." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:228 +msgid "External" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:230 +msgid "" +"Trigger automated actions based on a specific event in an external system or" +" application using a :doc:`webhook `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:233 +msgid "" +"After the webhook is configured in Odoo, where the webhook's URL is " +"generated and the target record defined, it needs to be implemented in the " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:237 +#: ../../content/applications/studio/automated_actions/webhooks.rst:6 +msgid "" +"It is *highly recommended* to consult with a developer, solution architect, " +"or another technical role when deciding to use webhooks and throughout the " +"implementation process. If not properly configured, webhooks may disrupt the" +" Odoo database and can take time to revert." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:245 +msgid "" +"It is also possible to set up an automated action that :ref:`sends data to a" +" external system's webhook ` when " +"an event occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:249 +msgid ":doc:`Webhook documentation `" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:254 +msgid "Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:256 +msgid "" +"Once you have defined the automation rule's :ref:`trigger `, click :guilabel:`Add an action` in the :guilabel:`Actions" +" To Do` tab to define the action to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:260 +msgid "" +"You can define multiple actions for the same automation rule. By default, " +"actions are executed in the order in which they were defined." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:263 +msgid "" +"This means, for example, that if you define an :guilabel:`Update record` " +"action and then a :guilabel:`Send email` action where the email references " +"the field that was updated, the email uses the updated values. However, if " +"the :guilabel:`Send email` action is defined before the :guilabel:`Update " +"record` action, the email uses the values set *before* the record is " +"updated." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:268 +msgid "" +"To change the order of defined actions, click the :icon:`oi-draggable` " +":guilabel:`(drag handle)` icon beside an action and drag it to the desired " +"position." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:274 +msgid "Update Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:276 +msgid "" +"This action updates one of the record's (related) fields. Click the " +":guilabel:`Update` field and, in the list that opens, select or search for " +"the field to be updated. If needed, click the :icon:`oi-chevron-right` " +":guilabel:`(right arrow)` next to the field name to access the list of " +"related fields." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:281 +msgid "" +"If you selected a :ref:`many2many field `, choose whether the field must be updated by :guilabel:`Adding`," +" :guilabel:`Removing`, or :guilabel:`Setting it to` the selected value or by" +" :guilabel:`Clearing it`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:286 +msgid "" +"If you want the automated action to remove a tag from the customer record, " +"set the :guilabel:`Update` field to :guilabel:`Customer > Tags`, select " +":guilabel:`by Removing`, then select the tag." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of an Update Record action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:294 +msgid "" +"Alternatively, you can also set a record's field dynamically using Python " +"code. To do so, select :guilabel:`Compute` instead of :guilabel:`Update`, " +"then enter the code to be used for computing the field's value. For example," +" if you want the automation rule to compute a custom :ref:`datetime field " +"` when a task's priority is set to " +"`High` (by starring the task), you can define the trigger " +":guilabel:`Priority is set to` to `High` and define the :guilabel:`Update " +"Record` action as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Compute a custom datetime field using a Python expression" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:307 +msgid "Create Activity" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:309 +msgid "" +"This action is used to schedule a new activity linked to the record. Select " +"an :guilabel:`Activity Type`, enter a :guilabel:`Title` and description, " +"then specify when you want the activity to be scheduled in the " +":guilabel:`Due Date In` field, and select a :guilabel:`User type`:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:313 +msgid "" +"To always assign the activity to the same user, select :guilabel:`Specific " +"User`, then add the user in the :guilabel:`Responsible` field;" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:315 +msgid "" +"To target a user linked to the record dynamically, select :guilabel:`Dynamic" +" User (based on record)` and change the :guilabel:`User Field` if necessary." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:319 +msgid "" +"After a lead is turned into an opportunity, you want the automated action to" +" set up a call for the user responsible for the lead. To do so, set the " +":guilabel:`Activity Type` to :guilabel:`Call` and the :guilabel:`User Type` " +"to :guilabel:`Dynamic User (based on record)`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:0 +msgid "Example of a Create Activity action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:329 +msgid "Send Email and Send SMS" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:331 +msgid "" +"These actions are used to send an email or a text message to a contact " +"linked to a specific record. To do so, select or create an :guilabel:`Email " +"Template` or an :guilabel:`SMS Template`, then, in the :guilabel:`Send Email" +" As` or :guilabel:`Send SMS As` field, choose how you want to send the email" +" or text message:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:336 +msgid "" +":guilabel:`Email`: to send the message as an email to the recipients of the " +":guilabel:`Email Template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:338 +msgid "" +":guilabel:`Message`: to post the message on the record and notify the " +"record's followers." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:339 +msgid "" +":guilabel:`Note`: to send the message as an internal note visible to " +"internal users in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:341 +msgid "" +":guilabel:`SMS (without note)`: to send the message as a text message to the" +" recipients of the :guilabel:`SMS template`." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:343 +msgid "" +":guilabel:`SMS (with note)`: to send the message as a text message to the " +"recipients of the :guilabel:`SMS template` and post it as an internal note " +"in the chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:345 +msgid "" +":guilabel:`Note only`: to only post the message as an internal note in the " +"chatter." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:350 +msgid "Send WhatsApp" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:353 +msgid "" +"To automate the sending of WhatsApp messages, one or more :ref:`WhatsApp " +"templates ` must be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:356 +msgid "" +"This action is used to send a WhatsApp message to a contact linked to a " +"specific record. To do so, select the appropriate :guilabel:`WhatsApp " +"Template` from the dropdown menu." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:362 +msgid "Add Followers and Remove Followers" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:364 +msgid "" +"This action is used to subscribe/unsubscribe existing contacts to/from the " +"record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:369 +msgid "Create Record" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:371 +msgid "This action is used to create a new record on any model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:373 +msgid "" +"Select the required model in the :guilabel:`Record to Create` field; it " +"contains the current model by default. Specify a :guilabel:`Name` for the " +"record, and then, if you want to create the record on another model, select " +"a field in the :guilabel:`Link Field` field to link the record that " +"triggered the creation of the new record." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:379 +msgid "" +"The dropdown list related to the :guilabel:`Link Field` field only contains " +":ref:`one2many fields ` existing " +"on the current model that are linked to a :ref:`many2one field " +"` on the target model." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:384 +msgid "" +"You can create another automation rule with :ref:`studio/automated-" +"actions/action-update-record` actions to update the fields of the new record" +" if necessary. For example, you can use a :guilabel:`Create Record` action " +"to create a new project task and then assign it to a specific user using an " +":guilabel:`Update Record` action." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:392 +msgid "Execute Code" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:395 +msgid "" +"For automation rules that require the execution of :ref:`custom code " +"`, note that maintenance of " +"custom code is not included in the *Standard* or *Custom* pricing plans and " +"incurs :ref:`additional fees `." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:400 +msgid "" +"This action is used to execute Python code. You can write your code into the" +" :guilabel:`Code` tab using the following variables:" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:403 +msgid "`env`: environment on which the action is triggered" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:404 +msgid "" +"`model`: model of the record on which the action is triggered; is a void " +"recordset" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:405 +msgid "`record`: record on which the action is triggered; may be void" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:406 +msgid "" +"`records`: recordset of all records on which the action is triggered in " +"multi-mode; this may be left empty" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:408 +msgid "`time`, `datetime`, `dateutil`, `timezone`: useful Python libraries" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:409 +msgid "" +"`float_compare`: utility function to compare floats based on specific " +"precision" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:410 +msgid "" +"`log(message, level='info')`: logging function to record debug information " +"in ir.logging table" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:412 +msgid "`_logger.info(message)`: logger to emit messages in server logs" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:413 +msgid "`UserError`: exception class for raising user-facing warning messages" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:414 +msgid "`Command`: x2many commands namespace" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:415 +msgid "`action = {...}`: to return an action" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:418 +msgid "" +"The available variables are described both in the :guilabel:`Code` and " +":guilabel:`Help` tabs." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:421 +msgid ":doc:`Odoo's ORM capabilities <../../developer/reference/backend/orm>`" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:426 +msgid "Send Webhook Notification" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:428 +msgid "" +"This action is used to send a `POST` API request with the values of the " +"selected :guilabel:`Fields` to the webhook URL specified in the " +":guilabel:`URL` field." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:431 +msgid "" +"The :guilabel:`Sample Payload` provides a preview of the data included in " +"the request using a random record's data or dummy data if no record is " +"available." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:435 +msgid "" +"It is also possible to set up an automated action that :doc:`uses a webhook " +"to receive data from an external system ` when a" +" predefined event occurs in that system." +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:441 +msgid "Execute Existing Actions" +msgstr "" + +#: ../../content/applications/studio/automated_actions.rst:443 +msgid "" +"The action is used to trigger multiple actions (linked to the current model)" +" at the same time. To do so, click on :guilabel:`Add a line`, then, in the " +":guilabel:`Add: Child Actions` pop-up, select an existing action or click " +":guilabel:`New` to create a new one." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:3 +msgid "Webhooks" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:10 +msgid "" +"Webhooks, which can be created in **Odoo Studio**, allow you to automate an " +"action in your Odoo database when a specific event occurs in another, " +"external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:13 +msgid "" +"In practice, this works as follows: when the event occurs in the external " +"system, a data file (the \"payload\") is sent to the Odoo webhook's URL via " +"a `POST` API request, and a predefined action is performed in your Odoo " +"database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:17 +msgid "" +"Unlike scheduled actions, which run at predefined intervals, or manual API " +"requests, which need to be explicitly invoked, webhooks enable real-time, " +"event-driven communication and automation. For example, you can set up a " +"webhook to have your Odoo inventory data updated automatically when a sales " +"order is confirmed in an external point-of-sale system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:22 +msgid "" +"Setting up a webhook in Odoo requires no coding when connecting two Odoo " +"databases, but :ref:`testing a webhook ` " +"requires an external tool. :ref:`Custom target records or actions " +"` may require programming skills." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:28 +msgid "" +"This article covers creating a webhook that *receives* data from an external" +" source. However, it is also possible to create an automated action that " +":ref:`sends data to an external webhook ` when a change occurs in your Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:35 +msgid "Create a webhook in Odoo" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:38 +msgid "" +"Before implementing a webhook in a live database, configure and test it " +"using a :ref:`duplicate database ` to " +"ensure the webhook performs as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:42 +msgid "" +":ref:`Activating developer mode ` before creating up a " +"webhook gives greater flexibility in selecting the :doc:`model " +"<../models_modules_apps>` the automation rule targets. It also allows you to" +" find the technical name of the model and fields, which may be needed to " +"configure the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:47 +msgid "" +"To find a model's technical name, with developer mode activated, hover over " +"the model name and then click :icon:`fa-arrow-right` :guilabel:`(Internal " +"link)`. The technical name can be found in the :guilabel:`Model` field. For " +"example, a sales order webhook uses the *Sales Order* model, but the " +"technical name `sale.order` is used in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:52 +msgid "To create a webhook in **Studio**, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:54 +msgid "" +":ref:`Open Studio ` and click :guilabel:`Webhooks`, then " +":guilabel:`New`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:55 +msgid "Give the webhook a clear, meaningful name that identifies its purpose." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:56 +msgid "" +"If needed, and provided developer mode is activated, select the appropriate " +":guilabel:`Model` from the dropdown. If developer mode is not activated, the" +" automation rule targets the current model by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:60 +msgid "" +"The webhook's URL is automatically generated, but can be changed if needed " +"by clicking :guilabel:`Rotate Secret`. This is the URL that should be used " +"when implementing the webhook in the external system that will send updates " +"to the database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:65 +msgid "" +"The URL is **confidential** and should be treated with care. Sharing it " +"online or without caution can provide unintended access to the Odoo " +"database. If the URL is updated after the initial implementation, make sure " +"to update it in the external system." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:69 +msgid "" +"If desired, enable :guilabel:`Log Calls` to track the history of API " +"requests made to the webhook's URL, e.g., for troubleshooting purposes." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:72 +msgid "" +"If the system sending the webhook is not Odoo, adjust the :guilabel:`Target " +"Record` code to look for the JSON record included in the payload when the " +"API request is made to the webhook's URL. If the system sending the webhook " +"is an Odoo database, ensure that the `id` and `model` appear in the payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:77 +msgid "" +"If the webhook is used to create records in the Odoo database, use " +"`model.browse(i)` or `model.search(i)` instead of the default " +":guilabel:`Target Record` format." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:80 +msgid "" +"Click :guilabel:`Add an action` in the :guilabel:`Actions To Do` tab to " +"define the :ref:`actions ` to be executed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:82 +msgid "" +"Before implementing the webhook in the external system, :ref:`test " +"` it to ensure it works as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:86 +msgid "" +"Webhooks can also be created via the :guilabel:`Automations` menu in " +"**Studio** by selecting the trigger :guilabel:`On webhook`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:88 +msgid "" +"To access the history of API requests if :guilabel:`Log Calls` has been " +"enabled, click the :guilabel:`Logs` smart button at the top of the " +":guilabel:`Automation rules` form." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:90 +msgid "" +"If the purpose of the webhook is anything other than to update an existing " +"record, e.g., to create a new record, the :guilabel:`Execute Code` action " +"must be chosen." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:96 +msgid "Test a webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:98 +msgid "" +"Testing a webhook requires a test payload and an external tool or system, " +"like `Postman `_, to send the payload via a `POST`" +" API request. This section presents the steps to test a webhook in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:103 +msgid "" +"See the :ref:`webhook use cases section ` " +"for step-by-step explanations of how to test webhooks using test payloads." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:105 +msgid "" +"To get specific help with testing a webhook with Postman, contact their " +"support team." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:107 +msgid "" +"In Postman, create a new HTTP request and set its method to " +":guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:108 +msgid "" +"Copy the webhook's URL from your Odoo database using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:110 +#: ../../content/applications/studio/automated_actions/webhooks.rst:192 +#: ../../content/applications/studio/automated_actions/webhooks.rst:267 +msgid "Click the :guilabel:`Body` tab and select :guilabel:`raw`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:111 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy the code from the test " +"payload and paste it into the code editor." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:113 +#: ../../content/applications/studio/automated_actions/webhooks.rst:206 +#: ../../content/applications/studio/automated_actions/webhooks.rst:281 +msgid "Click :guilabel:`Send`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:117 +msgid "" +"In the :guilabel:`Response` viewer at the bottom of the screen in Postman, " +"details, including a HTTP response code, indicate whether or not the webhook" +" is functioning correctly." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:120 +msgid "" +"A `200 OK` or `status: ok` message indicates that the webhook is functioning" +" properly on Odoo's side. From here, implementation can begin with the other" +" system to automatically send the API requests to the Odoo webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:124 +msgid "" +"If any other response is returned, the number associated with it helps to " +"identify the problem. For example, a `500 Internal Server Error` message " +"means that Odoo could not interpret the call properly. In this case, ensure " +"the fields found in the JSON file are properly mapped in the webhook's " +"configuration and in the system sending the test call." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:130 +msgid "" +"Turning on call logging in the webhook's configuration in Odoo provides " +"error logs if the webhook is not functioning as intended." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:134 +msgid "Implement a webhook in an external system" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:136 +msgid "" +"When the webhook has been successfully created in Odoo and tested, implement" +" it in the system that sends data to the Odoo database, making sure the " +"`POST` API requests are sent to the webhook's URL." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:142 +msgid "Webhook use cases" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:144 +msgid "" +"Below are two examples of how to use webhooks in Odoo. A test payload is " +"provided for each example, and can be found in the section on testing the " +"webhook. `Postman `_ is used to send the test " +"payload." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:149 +msgid "Update a sales order's currency" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:151 +msgid "" +"This webhook updates a sales order in the **Sales** app to `USD` when the " +"external system sends a `POST` API request to the webhook's URL that " +"includes that sales order number (which is identified by the payload's `id` " +"record)." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:155 +msgid "" +"This could be useful for subsidiaries outside the United States with a " +"mother company located inside the United States or during mergers when " +"consolidating data into one Odoo database." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:159 +#: ../../content/applications/studio/automated_actions/webhooks.rst:221 +msgid "Create the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:161 +#: ../../content/applications/studio/automated_actions/webhooks.rst:223 +msgid "To create this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:163 +msgid "" +"Open the **Sales** app, then :ref:`open Studio ` and click " +":guilabel:`Webhooks`. The *Sales Order* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:165 +#: ../../content/applications/studio/automated_actions/webhooks.rst:227 +msgid "" +"Click :guilabel:`New`. The :guilabel:`Trigger` is set to :guilabel:`On " +"webhook` by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:166 +msgid "" +"Set the :guilabel:`Target Record` to " +"`model.env[payload.get('model')].browse(int(payload.get('id')))`, where:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:169 +msgid "" +"`payload.get('model')` retrieves the value associated with the `model` key " +"in the payload, i.e., `sale.order`, which is the technical name of the " +"*Sales Order* model." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:171 +msgid "" +"`payload.get('id')` retrieves the value associated with the `id` key in the " +"payload, i.e., the number of the target sales order in your Odoo database " +"with the `S` and leading zeros removed." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:174 +msgid "" +"`int` converts the retrieved id to an integer (i.e., a whole number) because" +" the method `browse()` can only be used with an integer." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:177 +#: ../../content/applications/studio/automated_actions/webhooks.rst:231 +msgid "Click :guilabel:`Add an action`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:178 +msgid "In the :guilabel:`Type` section, click :guilabel:`Update Record`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:179 +msgid "" +"In the :guilabel:`Action details` section, select :guilabel:`Update`, choose" +" the field :guilabel:`Currency`, and select :guilabel:`USD`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:181 +#: ../../content/applications/studio/automated_actions/webhooks.rst:256 +msgid "Click :guilabel:`Save & Close`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:184 +#: ../../content/applications/studio/automated_actions/webhooks.rst:259 +msgid "Test the webhook" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:186 +#: ../../content/applications/studio/automated_actions/webhooks.rst:261 +msgid "To test this webhook, proceed as follows:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:188 +msgid "" +"With `Postman `_ open, create a new HTTP request " +"and set its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:190 +#: ../../content/applications/studio/automated_actions/webhooks.rst:265 +msgid "" +"Copy the URL of the Odoo webhook using the :icon:`fa-link` " +":guilabel:`(link)` icon and paste it into the URL field in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:193 +#: ../../content/applications/studio/automated_actions/webhooks.rst:268 +msgid "" +"Set the file type to :guilabel:`JSON`, then copy this code, i.e., the " +"payload, and paste it into the code editor:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:203 +msgid "" +"In your Odoo database, choose a sales order to test the webhook on. In the " +"pasted code, replace `SALES ORDER NUMBER` with the sales order's number " +"without the `S` or any zeros before the number. For example, a sales order " +"with the number `S00007` should be entered as `7` in Postman." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:207 +#: ../../content/applications/studio/automated_actions/webhooks.rst:282 +msgid "" +"Consult the :ref:`Response viewer ` " +"in Postman to determine whether or not the webhook is functioning properly. " +"If a message other than `200 OK` or `status: ok` is returned, the number " +"associated with the message helps to identify the problem." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:214 +msgid "Create a new contact" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:216 +msgid "" +"This webhook uses custom code to create a new contact in an Odoo database " +"when the external system sends a `POST` API request to the webhook's URL " +"that includes the contact's information. This could be helpful for " +"automatically creating new vendors or customers." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:225 +msgid "" +"Open the **Contacts** app, then :ref:`open Studio ` and click" +" :guilabel:`Webhooks`. The *Contact* model is selected by default." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:228 +msgid "" +"Set the :guilabel:`Target Record` to `model.browse([2])`. This is " +"essentially a placeholder as the code in the automated action tells the " +"webhook what needs to be retrieved from the payload and in which model the " +"record needs to be created." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:232 +msgid "In the :guilabel:`Type` section, click :guilabel:`Execute Code`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:233 +msgid "" +"Copy this code and paste it into the code editor in the :guilabel:`Code` tab" +" of the :guilabel:`Action details` section:" +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:263 +msgid "" +"In `Postman `_, create a new HTTP request and set " +"its method to :guilabel:`POST`." +msgstr "" + +#: ../../content/applications/studio/automated_actions/webhooks.rst:279 +msgid "" +"In the pasted code, replace the `CONTACT NAME`, `CONTACTEMAIL@EMAIL.COM`, " +"and `CONTACT PHONE NUMBER` with a new contact's information." +msgstr "" + +#: ../../content/applications/studio/fields.rst:3 +msgid "Fields and widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:5 +msgid "" +"Fields structure the models of a database. If you picture a model as a table" +" or spreadsheet, fields are the columns where data is stored in the records " +"(i.e., the rows). Fields also define the type of data that is stored within " +"them. How the data is presented and formatted on the :abbr:`UI (User " +"Interface)` is defined by their widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:10 +msgid "" +"From a technical point of view, there are 15 field types in Odoo. However, " +"you can choose from 20 fields in Studio, as some field types are available " +"more than once with a different default widget." +msgstr "" + +#: ../../content/applications/studio/fields.rst:14 +msgid "" +":guilabel:`New Fields` can only be added to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views. On other views, you can only add :guilabel:`Existing " +"Fields` :dfn:`(fields already on the model)`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:21 +msgid "Simple fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:23 +msgid "Simple fields contain basic values, such as text, numbers, files, etc." +msgstr "" + +#: ../../content/applications/studio/fields.rst:26 +msgid "" +"Non-default widgets, when available, are presented as bullet points or sub-" +"headings below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:31 +msgid "Text (`char`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:33 +msgid "" +"The :guilabel:`Text` field is used for short text containing any character. " +"One text line is displayed when filling out the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:36 +#: ../../content/applications/studio/fields.rst:258 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:38 +#: ../../content/applications/studio/fields.rst:70 +msgid "" +":guilabel:`Copy to Clipboard`: users can copy the value by clicking a " +"button." +msgstr "" + +#: ../../content/applications/studio/fields.rst:39 +msgid ":guilabel:`E-mail`: the value becomes a clickable *mailto* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:40 +msgid "" +":guilabel:`Image`: displays an image using a URL. The value cannot be edited" +" manually, but a default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:44 +msgid "" +"This works differently than selecting the :ref:`Image field " +"` directly, as the image is not stored in" +" Odoo when using a :guilabel:`Text` field with the :guilabel:`Image` widget." +" For example, it can be useful if you want to save disk space." +msgstr "" + +#: ../../content/applications/studio/fields.rst:49 +msgid ":guilabel:`Phone`: the value becomes a clickable *tel* link." +msgstr "" + +#: ../../content/applications/studio/fields.rst:52 +msgid "" +"Tick :guilabel:`Enable SMS` to add an option to send an SMS directly from " +"Odoo next to the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:55 +msgid ":guilabel:`URL`: the value becomes a clickable URL." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:65 +msgid "Multiline Text (`text`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:67 +msgid "" +"The :guilabel:`Multiline Text` field is used for longer text containing any " +"type of character. Two text lines are displayed on the UI when filling out " +"the field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Multiline Text fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:80 +msgid "Integer (`integer`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:82 +msgid "" +"The :guilabel:`Integer` field is used for all integer numbers " +"(:dfn:`positive, negative, or zero, without a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:85 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The value cannot be edited on the UI, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:87 +#: ../../content/applications/studio/fields.rst:115 +msgid "" +":guilabel:`Progress Bar`: displays the value next to a percentage bar, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:89 +msgid "" +":guilabel:`Handle`: displays a drag handle icon to order records manually in" +" :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Integer fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:100 +msgid "Decimal (`float`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:102 +msgid "" +"The :guilabel:`Decimal` field is used for all decimal numbers " +"(:dfn:`positive, negative, or zero, with a decimal`)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:106 +msgid "" +"Decimal numbers are displayed with two decimals after the decimal point on " +"the UI, but they are stored in the database with more precision." +msgstr "" + +#: ../../content/applications/studio/fields.rst:109 +msgid "" +":guilabel:`Monetary`: it is similar to using the :ref:`Monetary field " +"`. It is recommended to use the latter" +" as it offers more functionalities." +msgstr "" + +#: ../../content/applications/studio/fields.rst:112 +msgid "" +":guilabel:`Percentage`: displays a percent character `%` after the value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:113 +msgid "" +":guilabel:`Percentage Pie`: displays the value inside a percentage circle, " +"usually for a computed value. The field cannot be edited manually, but a " +"default value can be set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:117 +msgid "" +":guilabel:`Time`: the value must follow the *hh:mm* format, with a maximum " +"of 59 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Decimal fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:127 +msgid "Monetary (`monetary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:129 +msgid "The :guilabel:`Monetary` field is used for all monetary values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:132 +msgid "" +"When you first add a :guilabel:`Monetary` field, you are prompted to add a " +":guilabel:`Currency` field if none exists already on the model. Odoo offers " +"to add the :guilabel:`Currency` field for you. Once it is added, add the " +":guilabel:`Monetary` field again." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Monetary field along with its Currency field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:144 +msgid "Html (`html`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:146 +msgid "" +"The :guilabel:`Html` field is used to add text that can be edited using the " +"Odoo HTML editor." +msgstr "" + +#: ../../content/applications/studio/fields.rst:148 +msgid "" +":guilabel:`Multiline Text`: disables the Odoo HTML editor to allow editing " +"raw HTML." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Html fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:158 +msgid "Date (`date`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:160 +msgid "The :guilabel:`Date` field is used to select a date on a calendar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:162 +msgid "" +":guilabel:`Remaining Days`: the remaining number of days before the selected" +" date is displayed (e.g., *In 5 days*), based on the current date. This " +"field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:173 +msgid "Date & Time (`datetime`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:175 +msgid "" +"The :guilabel:`Date & Time` field is used to select a date on a calendar and" +" a time on a clock. The user's current time is automatically used if no time" +" is set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:180 +msgid "" +"As well as :ref:`general properties `, some " +":ref:`specific properties ` are " +"available for :guilabel:`Date & Time` fields that have the :guilabel:`Date &" +" Time` or :guilabel:`Date Range` widget set." +msgstr "" + +#: ../../content/applications/studio/fields.rst:186 +msgid "Date Range (`daterange`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:188 +msgid "" +"The :guilabel:`Date Range` widget is used to display a period of time " +"defined by a start date and an end date in a single line. A date range can " +"have a mandatory start and end date, e.g., for a multi-day event, or allow " +"an optional start or end date, e.g., for a field service intervention or a " +"project task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:193 +msgid "" +"Adding a date range requires two fields: a :guilabel:`Date & Time` field " +"with the :guilabel:`Date Range` widget set and another field that is " +"selected as the start date *or* end date. This underlying field can be an " +"existing :ref:`Date ` or :guilabel:`Date &" +" Time` field, or one created specifically for this purpose." +msgstr "" + +#: ../../content/applications/studio/fields.rst:198 +msgid "To add a date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:200 +msgid "" +"Identify an existing :guilabel:`Date` or :guilabel:`Date & Time` field that " +"can be used as the underlying start/end date field, or add a new one. If the" +" date range:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:203 +msgid "" +"has a mandatory start date and end date, this field can be either the start " +"date or end date; the outcome is the same." +msgstr "" + +#: ../../content/applications/studio/fields.rst:205 +msgid "" +"allows an optional start or end date, this field is the start date or end " +"date, respectively." +msgstr "" + +#: ../../content/applications/studio/fields.rst:208 +msgid "" +"To avoid displaying the same information twice, the underlying start/end " +"date field can be made invisible by enabling :guilabel:`Invisible` or " +"removed from the view by clicking :guilabel:`Remove from view`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:212 +msgid "" +"Add a :guilabel:`Date & Time` field and set the :guilabel:`Widget` field to " +":guilabel:`Date Range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:214 +msgid "Enter an appropriate :guilabel:`Label`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:215 +msgid "" +"Select the underlying start/end date field from the :guilabel:`Start date " +"field` or :guilabel:`End date field` dropdown, as relevant." +msgstr "" + +#: ../../content/applications/studio/fields.rst:217 +msgid "" +"If the date range should have a mandatory start and end date, enable " +":guilabel:`Always range`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:218 +msgid "" +"Update any other :ref:`general properties ` or " +"specific :ref:`properties for Date & Time fields ` as needed, then click :guilabel:`Close` in the upper right " +"corner of the screen." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Date & Time fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:228 +msgid "Remaining Days (`remaining_days`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:230 +msgid "" +"The :guilabel:`Remaining Days` widget displays the remaining number of days " +"before the selected date (e.g., *In 5 days*), based on the current date and " +"time. This field should be set to :guilabel:`Read only`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:237 +msgid "Checkbox (`boolean`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:239 +msgid "" +"The :guilabel:`Checkbox` field is used when a value should only be true or " +"false, indicated by checking or unchecking a checkbox." +msgstr "" + +#: ../../content/applications/studio/fields.rst:242 +msgid "" +":guilabel:`Button`: displays a radio button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:243 +msgid "" +":guilabel:`Toggle`: displays a toggle button. The widget works without " +"switching to the edit mode." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Checkbox fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:253 +msgid "Selection (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:255 +msgid "" +"The :guilabel:`Selection` field is used when users should select a single " +"value from a group of predefined values." +msgstr "" + +#: ../../content/applications/studio/fields.rst:260 +msgid "" +":guilabel:`Badges`: displays all selectable values simultaneously inside " +"rectangular shapes, organized horizontally." +msgstr "" + +#: ../../content/applications/studio/fields.rst:262 +msgid "" +":guilabel:`Priority`: displays star symbols instead of values, which can be " +"used to indicate an importance or satisfaction level, for example. This has " +"the same effect as selecting the :ref:`Priority field `, although, for the latter, four priority values are " +"already predefined." +msgstr "" + +#: ../../content/applications/studio/fields.rst:266 +#: ../../content/applications/studio/fields.rst:392 +msgid "" +":guilabel:`Radio`: displays all selectable values at the same time as radio " +"buttons." +msgstr "" + +#: ../../content/applications/studio/fields.rst:269 +msgid "" +"By default, radio buttons are organized vertically. Enable " +":guilabel:`Display horizontally` to switch the way they are displayed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:272 +msgid "" +":guilabel:`Status Bar`: displays all selectable values at the same time as " +"an arrow progress bar." +msgstr "" + +#: ../../content/applications/studio/fields.rst:275 +msgid "" +"By default, values on the status bar are selectable. Disable " +":guilabel:`Clickable` to prevent the value being edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of Selection fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:286 +msgid "Priority (`selection`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:288 +msgid "" +"The :guilabel:`Priority` field is used to display a three-star rating " +"system, which can be used to indicate importance or satisfaction level. This" +" field type is a :ref:`Selection field ` with the :guilabel:`Priority` widget selected by default and " +"four priority values predefined. Consequently, the :guilabel:`Badge`, " +":guilabel:`Badges`, :guilabel:`Radio`, and :guilabel:`Selection` widgets " +"have the same effects as described under :ref:`Selection " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:296 +msgid "" +"To change the number of available stars by adding or removing values, click " +":guilabel:`Edit Values`. Note that the first value is equal to 0 stars " +"(i.e., when no selection is made), so having four values results in a three-" +"star rating system, for example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Priority field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:308 +msgid "File (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:310 +msgid "" +"The :guilabel:`File` field is used to upload any type of file, or sign a " +"form (:guilabel:`Sign` widget)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:313 +msgid "" +":guilabel:`Image`: users can upload an image file, which is then displayed " +"in :ref:`Form view `. This has the same effect as" +" using the :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:316 +msgid "" +":guilabel:`PDF Viewer`: users can upload a PDF file, which can be then " +"browsed from the :ref:`Form view `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:318 +msgid "" +":guilabel:`Sign`: users can electronically sign the form. This has the same " +"effect as selecting the :ref:`Sign field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Examples of File fields with different widgets" +msgstr "" + +#: ../../content/applications/studio/fields.rst:329 +msgid "Image (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:331 +msgid "" +"The :guilabel:`Image` field is used to upload an image and display it in " +":ref:`Form view `. This field type is a " +":ref:`File field ` with the " +":guilabel:`Image` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`PDF Viewer`, and :guilabel:`Sign` widgets have " +"the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:338 +msgid "" +"To change the display size of uploaded images, select :guilabel:`Small`, " +":guilabel:`Medium`, or :guilabel:`Large` under the :guilabel:`Size` option." +msgstr "" + +#: ../../content/applications/studio/fields.rst:344 +msgid "Sign (`binary`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:346 +msgid "" +"The :guilabel:`Sign` field is used to sign the form electronically. This " +"field type is a :ref:`File field ` with " +"the :guilabel:`Sign` widget selected by default. Consequently, the " +":guilabel:`File`, :guilabel:`Image`, and :guilabel:`PDF Viewer` widgets have" +" the same effects as described under :ref:`File `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:352 +msgid "" +"To give users the :guilabel:`Auto` option when having to draw their " +"signature, select one of the available :guilabel:`Auto-complete with` fields" +" (:ref:`Text `, :ref:`Many2One " +"`, and :ref:`Related Field " +"` on the model only). The " +"signature is automatically generated using the data from the selected field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:361 +msgid "Relational fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:363 +msgid "" +"Relational fields are used to link and display the data from records on " +"another model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:366 +msgid "" +"Non-default widgets, when available, are presented as bullet points below." +msgstr "" + +#: ../../content/applications/studio/fields.rst:371 +msgid "Many2One (`many2one`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:373 +msgid "" +"The :guilabel:`Many2One` field is used to link another record (from another " +"model) to the record being edited. The record's name from the other model is" +" then displayed on the record being edited." +msgstr "" + +#: ../../content/applications/studio/fields.rst:377 +msgid "" +"On the *Sales Order* model, the :guilabel:`Customer` field is a " +":guilabel:`Many2One` field pointing at the *Contact* model. This allows " +"**many** sales orders to be linked to **one** contact (customer)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a many2one relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:385 +msgid "" +"To prevent users from creating a new record in the linked model, tick " +":guilabel:`Disable creation`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:387 +msgid "" +"To prevent users from opening records in a pop-up window, tick " +":guilabel:`Disable opening`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:388 +msgid "" +"To help users only select the right record, click on :guilabel:`Domain` to " +"create a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:390 +msgid "" +":guilabel:`Badge`: displays the value inside a rounded shape, similar to a " +"tag. The value cannot be edited on the UI." +msgstr "" + +#: ../../content/applications/studio/fields.rst:397 +msgid "One2Many (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:399 +msgid "" +"The :guilabel:`One2Many` field is used to display the existing relations " +"between a record on the current model and multiple records from another " +"model." +msgstr "" + +#: ../../content/applications/studio/fields.rst:403 +msgid "" +"You could add a :guilabel:`One2Many` field on the *Contact* model to look at" +" **one** customer's **many** sales orders." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing a one2many relationship" +msgstr "" + +#: ../../content/applications/studio/fields.rst:410 +msgid "" +"To use a :guilabel:`One2Many` field, the two models must have been linked " +"already using a :ref:`Many2One field `. One2Many relations do not exist independently: a reverse-search " +"of existing Many2One relations is performed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:417 +msgid "Lines (`one2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:419 +msgid "" +"The :guilabel:`Lines` field is used to create a table with rows and columns " +"(e.g., the lines of products on a sales order)." +msgstr "" + +#: ../../content/applications/studio/fields.rst:423 +msgid "" +"To modify the columns, click on the :guilabel:`Lines` field and then " +":guilabel:`Edit List View`. To edit the form that pops up when a user clicks" +" on :guilabel:`Add a line`, click on :guilabel:`Edit Form View` instead." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Lines field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:435 +msgid "Many2Many (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:437 +msgid "" +"The :guilabel:`Many2Many` field is used to link multiple records from " +"another model to multiple records on the current model. Many2Many fields can" +" use :guilabel:`Disable creation`, :guilabel:`Disable opening`, " +":guilabel:`Domain`, just like :ref:`Many2One fields " +"`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:443 +msgid "" +"On the *Task* model, the :guilabel:`Assignees` field is a " +":guilabel:`Many2Many` field pointing at the *Contact* model. This allows a " +"single user to be assigned to **many** tasks and **many** users to be " +"assigned to a single task." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Diagram showing many2many relationships" +msgstr "" + +#: ../../content/applications/studio/fields.rst:450 +msgid "" +":guilabel:`Checkboxes`: users can select several values using checkboxes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:451 +msgid "" +":guilabel:`Tags`: users can select several values appearing in rounded " +"shapes, also known as *tags*. This has the same effect as selecting the " +":ref:`Tags field `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:458 +msgid "Tags (`many2many`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:460 +msgid "" +"The :guilabel:`Tags` field is used to display several values from another " +"model appearing in rounded shapes, also known as *tags*. This field type is " +"a :ref:`Many2Many field ` with " +"the :guilabel:`Tags` widget selected by default. Consequently, the " +":guilabel:`Checkboxes` and :guilabel:`Many2Many` widgets have the same " +"effects as described under :ref:`Many2Many `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:467 +msgid "" +"To display tags with different background colors, tick :guilabel:`Use " +"colors`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:0 +msgid "Example of a Tags field" +msgstr "" + +#: ../../content/applications/studio/fields.rst:477 +msgid "Related Field (`related`)" +msgstr "" + +#: ../../content/applications/studio/fields.rst:479 +msgid "" +"A :guilabel:`Related Field` is not a relational field per se; no " +"relationship is created between models. It uses an existing relationship to " +"fetch and display information from another record." +msgstr "" + +#: ../../content/applications/studio/fields.rst:483 +msgid "" +"To display the email address of a customer on the *Sales Order* model, use " +"the :guilabel:`Related Field` `partner_id.email` by selecting " +":guilabel:`Customer` and then :guilabel:`Email`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:489 +msgid "Properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:492 +msgid "General properties" +msgstr "" + +#: ../../content/applications/studio/fields.rst:494 +msgid "" +":guilabel:`Invisible`: Enable this property when it is not necessary for " +"users to view a field on the UI. This helps declutter the UI by only showing" +" the essential fields depending on a specific situation." +msgstr "" + +#: ../../content/applications/studio/fields.rst:498 +msgid "" +"The :guilabel:`Invisible` attribute also applies inside Studio. To view " +"hidden fields in Studio, click on a view's :guilabel:`View` tab and enable " +":guilabel:`Show Invisible Elements`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:501 +msgid "" +":guilabel:`Required`: Enable this property if a field should always be " +"completed by the user before being able to proceed." +msgstr "" + +#: ../../content/applications/studio/fields.rst:504 +msgid "" +":guilabel:`Readonly`: Enable this property if users should not be able to " +"modify a field." +msgstr "" + +#: ../../content/applications/studio/fields.rst:507 +msgid "" +"You can choose to enable :guilabel:`Invisible`, :guilabel:`Required` and " +":guilabel:`Readonly` for specific records only by clicking on " +":guilabel:`Conditional` and creating a filter." +msgstr "" + +#: ../../content/applications/studio/fields.rst:511 +msgid "" +"On the *Form* view of the *Contact* model, the :guilabel:`Title` field only " +"appears when :guilabel:`Individual` is selected, as that field would not be " +"helpful for a :guilabel:`Company` contact." +msgstr "" + +#: ../../content/applications/studio/fields.rst:515 +msgid "" +":guilabel:`Label`: the field's name on the UI. This is not the name used in " +"the PostgreSQL database. To view and change the latter, activate the " +":ref:`developer mode ` and edit the :guilabel:`Technical " +"Name`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:519 +msgid "" +":guilabel:`Help Tooltip`: To explain the purpose of a field, add a " +"description. The text is displayed inside a tooltip box when hovering with " +"your mouse over the question mark beside the field's label." +msgstr "" + +#: ../../content/applications/studio/fields.rst:523 +msgid "" +":guilabel:`Widget`: To change the default appearance or functionality of a " +"field, select one of the available widgets." +msgstr "" + +#: ../../content/applications/studio/fields.rst:526 +msgid "" +":guilabel:`Placeholder`: To provide an example of how a field should be " +"completed, add placeholder text. The text appears in light gray until a " +"value is entered." +msgstr "" + +#: ../../content/applications/studio/fields.rst:529 +msgid "" +":guilabel:`Default value`: To display a default value in a field when a " +"record is created, add a value." +msgstr "" + +#: ../../content/applications/studio/fields.rst:532 +msgid "" +":guilabel:`Allow visibility to groups`: To limit which users can view the " +"field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:534 +msgid "" +":guilabel:`Forbid visibility to groups`: To prevent certain users from " +"seeing the field, select one or more user access :ref:`groups `." +msgstr "" + +#: ../../content/applications/studio/fields.rst:540 +msgid "Properties for Date & Time fields" +msgstr "" + +#: ../../content/applications/studio/fields.rst:542 +msgid "" +"For :guilabel:`Date & Time` fields that have the :guilabel:`Date & Time` or " +":guilabel:`Date Range` widget set, some specific properties are available:" +msgstr "" + +#: ../../content/applications/studio/fields.rst:545 +msgid "" +":guilabel:`Minimal precision`: Determine the smallest date unit that must be" +" selected in the date selector. The possible values are :guilabel:`Day`, " +":guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user must select a day in the date selector." +msgstr "" + +#: ../../content/applications/studio/fields.rst:548 +msgid "" +":guilabel:`Maximal precision`: Determine the largest date unit that can be " +"used to navigate the date selector. The possible values are :guilabel:`Day`," +" :guilabel:`Month`, :guilabel:`Year` or :guilabel:`Decade`. If no value is " +"selected, the user can navigate the date selector by decade." +msgstr "" + +#: ../../content/applications/studio/fields.rst:551 +msgid "" +":guilabel:`Warning for future dates`: Enable this property to display a " +"warning icon if a future date is selected." +msgstr "" + +#: ../../content/applications/studio/fields.rst:553 +msgid "" +":guilabel:`Condensed display`: Enable this property to show days, months and" +" hours with no leading zeros, e.g., `4/2/2025 8:05:00` instead of " +"`04/02/2025 08:05:00`." +msgstr "" + +#: ../../content/applications/studio/fields.rst:555 +msgid "" +":guilabel:`Show time`: This property is enabled by default for " +":guilabel:`Date & Time` fields. On a read-only field, disable the property " +"to show only the date. This can keep a list view less cluttered, for " +"example." +msgstr "" + +#: ../../content/applications/studio/fields.rst:558 +msgid "" +":guilabel:`Show seconds`: This property is enabled by default for " +":guilabel:`Date & Time` fields. Disable the property to show only hours and " +"minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:560 +msgid "" +":guilabel:`Time interval`: Enter a value to determine the minute intervals " +"shown in the time selector. For example, enter 15 to allow quarter-hour " +"intervals. The default value is set to 5 minutes." +msgstr "" + +#: ../../content/applications/studio/fields.rst:563 +msgid "" +":guilabel:`Earliest accepted date`: Enter the earliest date that can be " +"selected in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the " +"current date is always the earliest accepted date, enter `today`. On the " +"date selector, dates prior to the earliest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/fields.rst:567 +msgid "" +":guilabel:`Latest accepted date`: Enter the latest date that can be selected" +" in the date selector in ISO-format, i.e., `YYYY-MM-DD`. If the current date" +" is always the latest accepted date, enter `today`. On the date selector, " +"dates later than the latest accepted date are grayed out." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:3 +msgid "Models, modules, and apps" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:5 +msgid "" +"Models determine the logical structure of a database and how data is stored," +" organized, and manipulated. In other words, a model is a table of " +"information that can be linked with other tables. A model usually represents" +" a business concept, such as a *sales order*, *contact*, or *product*." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:9 +msgid "" +"Modules and apps contain various elements, such as models, views, data " +"files, web controllers, and static web data." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:13 +msgid "" +"All apps are modules. Larger, standalone modules are typically referred to " +"as apps, whereas other modules usually serve as add-ons to said apps." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:19 +msgid "Suggested features" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:21 +msgid "" +"When you create a new model or app with Studio, you can choose to add up to " +"14 features to speed up the creation process. These features bundle fields, " +"default settings, and views that are usually used together to provide some " +"standard functionality. Most of these features can be added later on, but " +"adding them from the start makes the model creation process much easier. " +"Furthermore, these features interact together in some cases to increase " +"their usefulness." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:28 +msgid "" +"Creating a model with the :ref:`studio/models-modules-apps/suggested-" +"features/picture` and :ref:`studio/models-modules-apps/suggested-" +"features/pipeline-stages` features enabled adds the image in the card layout" +" of the :ref:`Kanban view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "" +"Combination of the Picture and Pipeline stages features on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:39 +msgid "Contact details" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:41 +msgid "" +"Selecting :guilabel:`Contact details` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model " +"and two of its :ref:`Related Fields `: :guilabel:`Phone` and :guilabel:`Email`. The " +":guilabel:`Contact` field is also added to the :ref:`List view " +"`, and the :ref:`Map view " +"` is activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Contact details feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:57 +msgid "User assignment" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:59 +msgid "" +"Selecting :guilabel:`User assignment` adds to the :ref:`Form view " +"` a :ref:`Many2One field " +"` linked to the *Contact* model, " +"with the following :guilabel:`Domain`: `Share User is not set` to only allow" +" the selection of *Internal Users*. In addition, the " +":guilabel:`many2one_avatar_user` widget is used to display the user's " +"avatar. The :guilabel:`Responsible` field is also added to the :ref:`List " +"view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "User assignment feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:75 +msgid "Date & Calendar" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:77 +msgid "" +"Selecting :guilabel:`Date & Calendar` adds to the :ref:`Form view " +"` a :ref:`Date field ` and activates the :ref:`Calendar view " +"`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:84 +msgid "Date range & Gantt" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:86 +msgid "" +"Selecting :guilabel:`Date range & Gantt` adds to the :ref:`Form view " +"` two :ref:`Date fields ` next to each other: one to set a start date, the other to set " +"an end date, using the :guilabel:`daterange` widget, and activates the " +":ref:`Gantt view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:94 +msgid "Pipeline stages" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:96 +msgid "" +"Selecting :guilabel:`Pipeline stages` activates the :ref:`Kanban view " +"`, adds several fields such as " +":ref:`Priority ` and :guilabel:`Kanban" +" State`, and three stages: :guilabel:`New`, :guilabel:`In Progress`, and " +":guilabel:`Done`. The :guilabel:`Pipeline status bar` and the " +":guilabel:`Kanban State` field are added to the :ref:`Form view " +"`. The :guilabel:`Color` field is added to the " +":ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:105 +msgid "The :guilabel:`Pipeline stages` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:110 +msgid "Tags" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:112 +msgid "" +"Selecting :guilabel:`Tags` adds to the :ref:`studio/views/general/form` and " +":ref:`studio/views/multiple-records/list` views a :ref:`Tags field " +"`, creating a *Tag* model with " +"preconfigured access rights in the process." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:120 +msgid "Picture" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:122 +msgid "" +"Selecting :guilabel:`Picture` adds to the top-right of the :ref:`Form view " +"` an :ref:`Image field `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:126 +msgid "The :guilabel:`Picture` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:131 +msgid "Lines" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:133 +msgid "" +"Selecting :guilabel:`Lines`: adds to the :ref:`Form view " +"` a :ref:`Lines field ` inside a :guilabel:`Tab` component." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:139 +msgid "Notes" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:141 +msgid "" +"Selecting :guilabel:`Notes` adds to the :ref:`Form view " +"` an :ref:`Html field ` using the full width of the form." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:147 +msgid "Monetary value" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:149 +msgid "" +"Selecting :guilabel:`Monetary value` adds to the " +":ref:`studio/views/general/form` and :ref:`studio/views/multiple-" +"records/list` views a :ref:`Monetary field `. The :ref:`studio/views/reporting/graph` and " +":ref:`studio/views/reporting/pivot` views are also activated." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:155 +msgid "A *Currency* field is added and hidden from the view." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:160 +msgid "Company" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:162 +msgid "" +"Selecting :guilabel:`Company` adds to the :ref:`studio/views/general/form` " +"and :ref:`studio/views/multiple-records/list` views a :ref:`Many2One field " +"` linked to the *Company* model." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:167 +msgid "This is only useful if you work in a multi-company environment." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:172 +msgid "Custom Sorting" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:174 +msgid "" +"Selecting :guilabel:`Custom Sorting` adds to the :ref:`List view " +"` a drag handle icon to manually reorder" +" records." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Custom Sorting feature on the List view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:186 +msgid "Chatter" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:188 +msgid "" +"Selecting :guilabel:`Chatter` adds to the :ref:`Form view " +"` Chatter functionalities (sending messages, " +"logging notes, and scheduling activities)." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:192 +msgid "The :guilabel:`Chatter` feature can be added at a later stage." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:0 +msgid "Chatter feature on the Form view" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:203 +msgid "Archiving" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:205 +msgid "" +"Selecting :guilabel:`Archiving` adds to the :ref:`studio/views/general/form`" +" and :ref:`studio/views/multiple-records/list` views the :guilabel:`Archive`" +" action and hides archived records from searches and views by default." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:212 +msgid "Export and import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:214 +msgid "" +"When you do any customization with Studio, a new module named " +"`studio_customization` is added to your database. You can export this module" +" as a ZIP file using the :guilabel:`Studio Export` function. The module can " +"then be imported into another Odoo database. This may be useful, for " +"example, when setting up a new module or for training purposes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:220 +msgid "" +"Exporting and importing customizations in this way, rather than using the " +":doc:`standard Odoo export and import <../essentials/export_import_data>` " +"functions, means data is imported in a logical way. For example, if the " +"module contains customers and sales orders, the customers are created first," +" since these are required for the sales orders to be created." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:228 +msgid "Export customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:230 +msgid "" +"To export customizations, click the :icon:`oi-studio` :guilabel:`(Toggle " +"Studio)` button on the main Odoo dashboard, then :guilabel:`Export`, then " +"either:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:233 +msgid "" +"download all Studio customizations by clicking the :guilabel:`Export` " +"button; or" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:234 +msgid "" +"choose what data to export by clicking :ref:`Configure data and demo data to" +" export `." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:240 +msgid "Configure data to export" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:242 +msgid "" +"To select specific models to export, click :guilabel:`New` on the " +":guilabel:`Studio Export` screen, then start typing the name of the relevant" +" model or select it from the list." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:246 +msgid "" +"Click :guilabel:`Preset` to see a list of all models in your database with " +"records that have been modified using Studio and all custom models created " +"using Studio. To configure one of these models for export, click on the " +"model to open it and make the required changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:250 +msgid "Tick the following options as relevant:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:252 +msgid "" +":guilabel:`Demo`: if the exported records should be considered as demo data " +"when imported." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:253 +msgid "" +":guilabel:`Attachments`: if attachments related to exported records should " +"be included in the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:255 +msgid "" +":guilabel:`Updatable`: if the exported records should be able to be updated " +"during a module update." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:257 +msgid "" +"If necessary, edit the :guilabel:`Domain` to determine which of the model's " +"records should be exported. To do so, click the :guilabel:`Edit Domain` " +"button or :icon:`fa-caret-right` :guilabel:`(Modify filter)` then " +":guilabel:`Edit Domain`, as appropriate. Proceed to make any required " +"changes." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:262 +msgid "" +"After configuring a model for export, click :guilabel:`Studio Export` to " +"return to the main screen. To download a ZIP file with the customizations " +"for all the listed models, click :guilabel:`Export`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:266 +msgid "" +"It is not necessary to select one or more models as all listed models will " +"be included in the export. To remove a model from the export, select it and " +"click the :icon:`fa-cog` :guilabel:`Actions` button then :icon:`fa-trash-o` " +":guilabel:`Delete`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:270 +msgid "In the :guilabel:`Studio Export` window:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:272 +msgid "" +"leave the checkboxes unticked to export only the customizations done with " +"Studio." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:273 +msgid "" +"tick :guilabel:`Include Data` to include data from the selected models in " +"the export." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:274 +msgid "" +"tick :guilabel:`Include Demo Data` to include data from the selected models " +"that is flagged as demo data. Ticking this option also ticks " +":guilabel:`Include Data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:277 +msgid "Click the :guilabel:`Export` button to download the ZIP file." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:-1 +msgid "Choosing to export both data and demo data" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:285 +msgid "Import customizations" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:288 +msgid "" +"Before importing, make sure the destination database is on the same Odoo " +"version and contains the same apps and modules as the source database. " +"Studio does not add the underlying modules as dependencies of the exported " +"module." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:292 +msgid "To import and install Studio customizations in another Odoo database:" +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:294 +msgid "Connect to the destination database." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:295 +msgid "" +"Click the :icon:`oi-studio` :guilabel:`(Toggle Studio)` button on the main " +"Odoo dashboard, then :guilabel:`Import`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:297 +msgid "" +"Upload the exported ZIP file. If demo data should be imported, tick " +":guilabel:`Load demo data`." +msgstr "" + +#: ../../content/applications/studio/models_modules_apps.rst:298 +msgid "Click :guilabel:`Install`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:3 +msgid "PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:5 +msgid "" +"With Studio, you can :ref:`edit existing PDF reports ` (e.g., invoices, quotations, etc.) or :ref:`create new ones " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:11 +msgid "Default layout" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:13 +msgid "" +"The default layout of reports is managed outside Studio. Go to " +":menuselection:`Settings`, then, in the :guilabel:`Companies` section of the" +" main page, click :guilabel:`Configure Document Layout`. Layout settings are" +" company-specific but apply to all reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:18 +msgid "" +"You can see how the different settings affect the report layout in the " +"report preview on the right side of the :guilabel:`Configure your document " +"layout` window. When creating or editing a report, you can see a preview of " +"the report by clicking :guilabel:`Print preview` on the left side of the " +"screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:23 +msgid "Use the following settings:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:27 +msgid ":guilabel:`Layout`: Seven layouts are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:31 +msgid "Light" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Light report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:37 +msgid "Boxed" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Boxed report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:43 +msgid "Bold" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bold report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:49 +msgid "Striped" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Striped report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:55 +msgid "Bubble" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Bubble report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:61 +msgid "Wave" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Wave report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:67 +msgid "Folder" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Folder report layout sample" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:75 +msgid ":guilabel:`Background`: The following backgrounds are available:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:77 +msgid ":guilabel:`Blank`: Nothing is displayed." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:78 +msgid ":guilabel:`Demo logo`: A demo logo is displayed in the background." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:79 +msgid ":guilabel:`Custom`: Upload a custom background image." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:83 +msgid "" +":guilabel:`Text`: Eight fonts are available: Lato, Roboto, Open Sans, " +"Montserrat, Oswald, Raleway, Tajawal (which supports Arabic and Latin " +"scripts), and Fira Mono. Go to the `Google Fonts website " +"`_ to preview them." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:89 +msgid "" +":guilabel:`Company logo`: Click the :guilabel:`Edit` button to upload or " +"change the logo. This adds the logo to the company’s record on the *Company*" +" model, which you can access by going to :menuselection:`Settings` and then " +"clicking :guilabel:`Update Info` in the :guilabel:`Companies` section." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:96 +msgid "" +":guilabel:`Colors`: Change the primary and secondary colors used to " +"structure reports. The default colors are automatically generated based on " +"the colors of the logo." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:101 +msgid "" +":guilabel:`Address`: The company name and address are displayed in the " +"header of :ref:`external reports `. You " +"can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:106 +msgid "" +":guilabel:`Tagline`: This is displayed in the header of :ref:`external " +"reports ` using the Light, Striped, " +"Bubble, Wave and Folder layouts and in the footer of external reports using " +"the Boxed and Bold layouts. You can add multiple lines of text." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:113 +msgid "" +":guilabel:`Footer`: This text is used in the footer of :ref:`external " +"reports `. You can add multiple lines of " +"text. You can also edit the footer using the :ref:`report editor " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:119 +msgid "" +":guilabel:`Paper format`: This defines the default paper size of reports. " +"You can select :guilabel:`A4` (21 cm x 29.7 cm) and :guilabel:`US Letter` " +"(21.59 cm x 27.54 cm). This can also be defined for individual reports in " +"the :guilabel:`Paper format` field in :ref:`Studio `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:125 +msgid "" +"Other paper formats may be available depending on which apps or modules you " +"have installed, for example, label sheets for the Inventory app or event " +"badges for the Events app." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:131 +msgid "Creating new PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:133 +msgid "" +"To create a new report for a :doc:`model " +"`, (e.g., sales orders) access the" +" model, click the :icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then" +" click :guilabel:`Reports`. Click :guilabel:`New` and, in the popup window " +"that opens, select the type of report. This is solely used to determine what" +" is displayed in the header and footer:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:141 +msgid ":guilabel:`External`:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:143 +msgid "" +"The header displays the company's :ref:`logo ` and its :ref:`name and address `. For reports using the Light, Striped, Bubble, Wave and " +"Folder layouts, the :ref:`tagline ` also appears in the header." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:148 +msgid "" +"The footer displays the values set in the :ref:`Footer ` field and the page number. For reports using" +" the Boxed and Bold layouts, the :ref:`tagline ` also appears in the footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:153 +msgid "" +":guilabel:`Internal`: The header displays the user's current date and time, " +"the company's :ref:`name and address ` and the page number. There is no footer." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:157 +msgid "" +":guilabel:`Blank`: There is neither a header nor a footer. Click in the " +"upper left corner of the page to edit the report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:160 +msgid "" +"Once you have created the report, you can start :ref:`editing it " +"`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:165 +msgid "Editing PDF reports" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:167 +msgid "" +"To access the reports available for a model, access the model, click the " +":icon:`oi-studio` (:guilabel:`Toggle Studio`) button, then click " +":guilabel:`Reports`. Select an existing report to open it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:171 +msgid "" +"Alternatively, you can also open Studio, click :guilabel:`Reports`, and " +"search for a specific report or model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:175 +msgid "" +"It is strongly recommended to **duplicate** the standard report and make " +"changes in the duplicated version. To duplicate a report, hover the mouse " +"pointer on the top right corner of the report, click the :icon:`fa-ellipsis-" +"vertical` (:guilabel:`vertical ellipsis`) icon, and then select " +":guilabel:`Duplicate`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Duplicating a PDF report" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:186 +msgid "Options" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:188 +msgid "" +"Once you have selected or created a report, you can use the options in the " +"left part of the screen to:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:191 +msgid "" +"Change the :guilabel:`Report name`: The new name is applied everywhere (in " +"Studio, in the :guilabel:`Print` menu under the :icon:`fa-cog` " +"(:guilabel:`gear`) icon in the form view, and in the PDF file name)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:194 +msgid "" +"Modify the :guilabel:`Paper format`: If no value is selected, the format " +"defined in the :ref:`default layout ` is used." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:196 +msgid "" +":guilabel:`Show in print menu`: to add the report to the :guilabel:`Print` " +"menu in the form view." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:197 +msgid "" +":guilabel:`Reload from attachment`: to save the report as an attachment on " +"the record the first time it is generated and reload the original version of" +" the report any subsequent time. This is legally required for invoices and " +"is mainly used in this case." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:200 +msgid "" +":guilabel:`Limit visibility to groups`: to limit the availability of the PDF" +" report to specific :doc:`user groups <../general/users/access_rights>`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:202 +msgid "" +":guilabel:`Edit sources`: to modify the report directly in the :ref:`XML " +"file `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:204 +msgid "" +":guilabel:`Reset report`: to discard all changes made to the report and " +"reset it to its standard version." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:206 +msgid ":guilabel:`Print preview`: to generate and download a report preview." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:211 +msgid "Report editor" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:213 +msgid "" +"The report editor allows you to modify the content and formatting of the " +"report." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:216 +msgid "" +"You can :guilabel:`Undo` or :guilabel:`Redo` changes using the related " +"buttons or the shortcuts `CTRL` + `Z` and `CTRL` + `Y`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:219 +msgid "" +"Changes are saved automatically when you leave the report or manually using " +"the :guilabel:`Save` button." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:222 +msgid "" +"You can reset the report to its standard version by clicking the " +":guilabel:`Reset report` button in the left part of the screen." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:226 +msgid "" +"Editing the header and footer of a report impacts all standard and custom " +"reports." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:229 +msgid "Conditional blocks" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:231 +msgid "" +"The dashed rectangles represent **conditional blocks** (*if/else* " +"statements). These are used to show/hide content based on specific " +"conditions. Click on the block to view the conditions." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "View conditions applied to a block." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:237 +msgid "" +"Select a value to preview its corresponding output and edit it if necessary." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Preview the output of another condition." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:243 +msgid "" +"Conditions can only be edited in the :ref:`XML `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:246 +msgid "Other content" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:248 +msgid "There are two types of text content in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:250 +msgid "" +"Static text, i.e., the text that is not highlighted in blue, which can be " +"modified directly in the editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:252 +msgid "" +"Dynamic text, i.e., the text that is highlighted in blue, which is replaced " +"by :doc:`field ` values when the report is " +"generated, e.g., the sales order number or the quotation date." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:256 +msgid "" +"You can add content (e.g., fields, lists, tables, images, banners, etc.) to " +"the report using commands. Type `/` to open the :ref:`powerbox " +"`, then type the command's name or select " +"it from the list." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:260 +msgid "To add static text to the report, type the text where you want it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:262 +msgid "" +"For more advanced changes, you can :ref:`edit the report in the XML directly" +" `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:268 +msgid "Add a field" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:270 +msgid "" +"To add a field, type `/` and select the :guilabel:`Field` command. In the " +"list that opens, select or search for the field; click the right arrow next " +"to the field name to access the list of related fields if needed. Then, " +"specify the default value that will be shown if the field is not completed " +"in the record and press `Enter`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "Select a related field." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:281 +msgid "Add or edit a table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:283 +msgid "There are two types of tables in reports:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:285 +msgid "" +":ref:`Static tables `, which are used to " +"display static text or fields. For this type of table, you define the number" +" of columns and rows when adding the table." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:287 +msgid "" +":ref:`Dynamic tables `, which are used to " +"display data from :ref:`relational fields `. For this type of table, you only define the number of columns when" +" adding the table. The number of rows in the generated report will be " +"determined by the number of records in the related model that are linked " +"with the current model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:294 +msgid "" +"In a sales order report, a dynamic table is used to show the order lines " +"related to the sales order. If the sales order contains 10 order lines, the " +"table in the generated report has 10 rows; if it contains two order lines, " +"the table has two rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:301 +msgid "Add or edit a static table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:303 +msgid "" +"To add a static table, type `/` and select the :guilabel:`Table` command. " +"Determine the number of columns and rows for the table. Once the table has " +"been added, you can start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:306 +msgid "" +"You can insert, move and delete columns and rows using the table tools. " +"Position the cursor on top of the column or to the left of the row then " +"click the purple rectangle and select an option." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available options for editing table structure." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:312 +msgid "" +"To resize a column, drag the column border to the desired position; reset " +"all columns to their standard size by selecting :guilabel:`Reset Size` from " +"the table tools." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:315 +msgid "" +"Add the :ref:`field of your choice ` in a cell" +" or add static text by typing." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:319 +msgid "" +"To add text in a structured way without using a table, you can use columns. " +"Add columns by typing `/` and selecting the appropriate command: " +":guilabel:`2 columns`, :guilabel:`3 columns` or :guilabel:`4 columns`." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:326 +msgid "Add or edit a dynamic table" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:329 +msgid "" +"Only relations of type `one2many` or `many2many` can be displayed as dynamic" +" tables." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:330 +msgid "" +"An existing dynamic table in a standard report has a more complex structure " +"than a dynamic table you add yourself. For such tables, it is possible to " +"insert or delete columns; it is not possible to move columns or to insert, " +"move or delete rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:334 +msgid "" +"To add a dynamic table, type `/` and select the :guilabel:`Dynamic Table` " +"command. In the list that opens, select or search for the relation the table" +" will be based on and press `Enter`. Once the table has been added, you can " +"start editing it." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:338 +msgid "" +"You can insert, move and delete columns using the table tools, as for a " +":ref:`static table `. It is also possible " +"to insert static rows that will appear above or below the generated rows." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:342 +msgid "" +"To add a field to a cell, delete any placeholder text then add the " +":ref:`field of your choice `. The dialog box " +"that opens shows the source object for the field (e.g., the *Order Lines* " +"model) and the list of available fields." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:-1 +msgid "List of available fields for the sale order lines model." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:349 +msgid "Replace the :guilabel:`Column name` label by the label of your choice." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:352 +msgid "" +"The default row automatically iterates over the field's content, generating " +"a row on the report for each field value (e.g., one row per order line)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:356 +msgid "Formatting" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:358 +msgid "" +"To format text in the report, select it, then format it using the options in" +" the :doc:`text editor `." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Format text using the text editor." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:367 +msgid "Editing the report's XML" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:370 +msgid "" +"Modifying the XML directly may result in report issues during :doc:`upgrades" +" <../../../administration/upgrade>`. If this happens, simply copy your " +"changes from the old database into your upgraded database." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:374 +msgid "" +"To edit the report's XML, click :guilabel:`Edit sources` in the left pane." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:377 +msgid "Examples" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:381 +msgid "" +"To change how data is presented in your report, you can modify a field's " +"default :doc:`widget ` manually. In the example" +" below, the order date shows the date and time by default, while the unit " +"price defaults to a precision of two decimal places." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:394 +msgid "" +"By using `t-options`, in this case the `widget` option, these fields can be " +"modified to show only the date and a precision of four decimal places, " +"respectively:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:407 +msgid "" +"If you want to show/hide content based on specific conditions, you can " +"manually add `if/else` control statements in the report XML." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:410 +msgid "" +"For example, if you want to hide a custom data table if there are no tags, " +"you can use the `t-if` attribute to define the condition, which is then " +"evaluated as `True` or `False`. The table will not be displayed if there are" +" no tags in the quotation." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:439 +msgid "" +"If you want to display another block in case the `t-if` statement is " +"evaluated as `False`, you can specify it using the `t-else` statement. The " +"`t-else` block must directly follow the `t-if` block in the document " +"structure. There is no need to specify any condition in the `t-else` " +"attribute. As an example, let's show a quick message explaining that there " +"are no tags on the quotation:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:471 +msgid "" +"By using the `t-if/t-else` notation, the report editor recognizes that these" +" sections are mutually exclusive and should be displayed as conditional " +"blocks:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:477 +msgid "You can switch conditions using the editor to preview their output:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Output preview if there are no tags." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:482 +msgid "" +"If you wish to have multiple options, you can also use `t-elif` directives " +"to add intermediary conditions. For example, this is how the title of sales " +"order reports changes based on the condition of the underlying document." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:495 +msgid "" +"The title *Pro-Forma Invoice* is used depending on some contextual " +"conditions. If these conditions are not met and the state of the document is" +" either `draft` or `sent`, then *Quotation* is used. If none of those " +"conditions are met, the report's title is *Order*." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:501 +msgid "" +"Working with images in a report can be challenging, as precise control over " +"image size and behavior is not always obvious. You can insert image fields " +"using the report editor (by using the :ref:`Field command `), but inserting them in XML using the `t-field` " +"directive and accompanying `t-options` attributes provides better sizing and" +" positioning control." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:507 +msgid "" +"For example, the following code outputs the field `image_128` of the line's " +"product as a 64px-wide image (with an automatic height based on the image's " +"aspect ratio)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:514 +msgid "The following options are available for image widgets:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:516 +msgid "" +"`width`: width of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-width)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:518 +msgid "" +"`height`: height of the image, usually in pixels or CSS length units (e.g., " +"`rem`) (leave empty for auto-height)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:520 +msgid "" +"`class`: CSS classes applied on the `img` tag; `Bootstrap classes " +"`_ are available." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:522 +msgid "`alt`: alternative text of the image" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:523 +msgid "" +"`style`: style attribute; it allows you to override styles more freely than " +"with `Bootstrap classes " +"`_." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:526 +msgid "" +"These attributes must contain strings, i.e., text enclosed within quotes " +"within quotes, e.g., `t-options-width=\"'64px'\"` (or, alternatively, a " +"valid Python expression)." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:530 +msgid "" +"The image widget cannot be used on an `img` tag. Instead, set the `t-field` " +"directive on a `span` (for inline content) or `div` (for block content) " +"node." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:533 +msgid "" +"For example, let's add a column with the product image in the quotation " +"table:" +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:561 +msgid "" +"The `t-options-width` attribute restricts the image width to 64 pixels, and " +"the Bootstrap classes used in `t-options-class` create a thumbnail-like " +"border with rounded corners and a shadow." +msgstr "" + +#: ../../content/applications/studio/pdf_reports.rst:0 +msgid "Add a column with the product image in the quotation table." +msgstr "" + +#: ../../content/applications/studio/views.rst:3 +msgid "Views" +msgstr "" + +#: ../../content/applications/studio/views.rst:5 +msgid "" +"Views are the interface that allows displaying the data contained in a " +":doc:`model `. One model can have several views, which " +"are simply different ways to show the same data. In Studio, views are " +"organized into four categories: :ref:`general `, " +":ref:`multiple records `, :ref:`timeline " +"`, and :ref:`reporting `." +msgstr "" + +#: ../../content/applications/studio/views.rst:12 +msgid "" +"To change the default view of a model, :ref:`access Studio `," +" go to :guilabel:`Views`, click the :icon:`fa-ellipsis-v` " +"(:guilabel:`ellipsis`) icon next to the desired view, and click " +":guilabel:`Set as Default`." +msgstr "" + +#: ../../content/applications/studio/views.rst:15 +msgid "" +"You can modify views using the built-in XML editor: Activate the " +":ref:`Developer mode `, go to the view you want to edit, " +"select the :guilabel:`View` tab, and click :guilabel:` XML`." +msgstr "" + +#: ../../content/applications/studio/views.rst:20 +msgid "" +"If you are editing a view using the XML editor, avoid making changes " +"directly to standard and inherited views, as these would be reset and lost " +"during updates or module upgrades. Always make sure you select the right " +"Studio inherited views: When you modify a view in Studio by dragging and " +"dropping a new field, for example, a specific Studio inherited view and its " +"corresponding XPath, which defines the modified part of the view, are " +"automatically generated." +msgstr "" + +#: ../../content/applications/studio/views.rst:30 +msgid "General views" +msgstr "" + +#: ../../content/applications/studio/views.rst:33 +#: ../../content/applications/studio/views.rst:106 +#: ../../content/applications/studio/views.rst:207 +#: ../../content/applications/studio/views.rst:322 +msgid "" +"The settings described below are found under the view's :guilabel:`View` tab" +" unless specified otherwise." +msgstr "" + +#: ../../content/applications/studio/views.rst:39 +msgid "Form" +msgstr "" + +#: ../../content/applications/studio/views.rst:41 +msgid "" +"The :guilabel:`Form` :icon:`fa-address-card` view is used when creating and " +"editing records, such as contacts, sales orders, products, etc." +msgstr "" + +#: ../../content/applications/studio/views.rst:44 +msgid "" +"To structure a form, drag and drop the :guilabel:`Tabs and Columns` element " +"found under the :guilabel:`+ Add` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:46 +#: ../../content/applications/studio/views.rst:139 +msgid "" +"To prevent users from creating, editing, or deleting records, untick " +":guilabel:`Can Create`, :guilabel:`Can Edit`, or :guilabel:`Can Delete`." +msgstr "" + +#: ../../content/applications/studio/views.rst:48 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the form, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:51 +#: ../../content/applications/studio/views.rst:155 +msgid "" +":guilabel:`Run a Server Action`: select the :ref:`server action " +"` to be executed from the dropdown list;" +msgstr "" + +#: ../../content/applications/studio/views.rst:53 +#: ../../content/applications/studio/views.rst:157 +msgid "" +":guilabel:`Call a method`: specify an existing Python method already defined" +" in Odoo." +msgstr "" + +#: ../../content/applications/studio/views.rst:55 +msgid "" +"To change a button's label or style, click the button and edit its " +":guilabel:`Label` or :guilabel:`Class` (either `btn-primary` or `btn-" +"secondary`) in the :guilabel:`Properties` tab." +msgstr "" + +#: ../../content/applications/studio/views.rst:57 +msgid "" +"To add a smart button, click the :icon:`fa-plus-square` (:guilabel:`plus`) " +"icon in the top-right corner of the form. Enter a :guilabel:`Label`, choose " +"an :guilabel:`Icon`, and select a :ref:`related field " +"`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's Form view" +msgstr "" + +#: ../../content/applications/studio/views.rst:69 +msgid "Activity" +msgstr "" + +#: ../../content/applications/studio/views.rst:71 +msgid "" +"The :guilabel:`Activity` :icon:`fa-clock-o` view is used to schedule and " +"have an overview of activities (emails, calls, etc.) linked to records." +msgstr "" + +#: ../../content/applications/studio/views.rst:75 +msgid "This view can only be modified within Studio by editing the XML code." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Lead/Opportunity model's Activity view" +msgstr "" + +#: ../../content/applications/studio/views.rst:85 +msgid "Search" +msgstr "" + +#: ../../content/applications/studio/views.rst:87 +msgid "" +"The :guilabel:`Search` :icon:`oi-search` view is added on top of other views" +" to filter, group, and search records." +msgstr "" + +#: ../../content/applications/studio/views.rst:90 +msgid "" +"To add custom :guilabel:`Filters` and structure them using " +":guilabel:`Separators`, go to the :guilabel:`+ Add` tab and drag and drop " +"them under :guilabel:`Filters`." +msgstr "" + +#: ../../content/applications/studio/views.rst:92 +msgid "" +"To add an existing field under the search dropdown menu, go to the " +":guilabel:`+ Add` tab and drag and drop it under :guilabel:`Autocompletion " +"Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Search view on the Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:103 +msgid "Multiple records views" +msgstr "" + +#: ../../content/applications/studio/views.rst:112 +msgid "Kanban" +msgstr "" + +#: ../../content/applications/studio/views.rst:114 +msgid "" +"The :guilabel:`Kanban` :icon:`oi-view-kanban` view is often used to support " +"business flows by moving records across stages or as an alternative way to " +"display records inside *cards*." +msgstr "" + +#: ../../content/applications/studio/views.rst:118 +msgid "" +"If the :guilabel:`Kanban` view exists, it is used by default to display data" +" on mobile devices instead of the :ref:`List view `." +msgstr "" + +#: ../../content/applications/studio/views.rst:121 +msgid "" +"To prevent users from creating new records, untick :guilabel:`Can Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:122 +msgid "" +"To create records directly within the view, in a minimalistic form, enable " +":guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:124 +#: ../../content/applications/studio/views.rst:151 +msgid "" +"To set a default grouping for records, select a field under " +":guilabel:`Default Group By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Project model's Kanban view" +msgstr "" + +#: ../../content/applications/studio/views.rst:134 +msgid "List" +msgstr "" + +#: ../../content/applications/studio/views.rst:136 +msgid "" +"The :guilabel:`List` :icon:`oi-view-list` view is used to overview many " +"records at once, look for records, and edit simple records." +msgstr "" + +#: ../../content/applications/studio/views.rst:141 +msgid "" +"To create and edit records directly within the view, select either " +":guilabel:`Add record at the bottom`, :guilabel:`Add record on top` or " +":guilabel:`Open form view` under :guilabel:`When Creating Record`." +msgstr "" + +#: ../../content/applications/studio/views.rst:146 +msgid "" +"This prevents users from opening records in :ref:`Form view " +"` from the :guilabel:`List` view." +msgstr "" + +#: ../../content/applications/studio/views.rst:149 +msgid "To edit several records at once, tick :guilabel:`Enable Mass Editing`." +msgstr "" + +#: ../../content/applications/studio/views.rst:150 +msgid "" +"To change the way records are sorted by default, select a field under " +":guilabel:`Sort By`." +msgstr "" + +#: ../../content/applications/studio/views.rst:152 +msgid "" +"To add a button, click :guilabel:`Add a button` at the top of the list, " +"enter a :guilabel:`Label`, and select the button's action:" +msgstr "" + +#: ../../content/applications/studio/views.rst:160 +msgid "" +"To add a :icon:`oi-draggable` (:guilabel:`drag handle`) icon to reorder " +"records manually, add an :ref:`Integer field ` with the :guilabel:`Handle` widget." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Drag handle icon enabling to sort records manually in List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales order model's List view" +msgstr "" + +#: ../../content/applications/studio/views.rst:174 +msgid "Map" +msgstr "" + +#: ../../content/applications/studio/views.rst:176 +msgid "" +"The :guilabel:`Map` :icon:`fa-map-marker` view is used to display records on" +" a map. For example, it is used in the Field Service app to plan an " +"itinerary between different tasks." +msgstr "" + +#: ../../content/applications/studio/views.rst:180 +msgid "" +"A :ref:`Many2One field ` linked to" +" the *Contact* model is required to activate the view, as the contact " +"address is used to position records on the map." +msgstr "" + +#: ../../content/applications/studio/views.rst:183 +msgid "" +"To select which kind of contact should be used on the map, select it under " +":guilabel:`Contact Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:185 +msgid "" +"To hide the name or the address of the record, tick :guilabel:`Hide Name` or" +" :guilabel:`Hide Address`." +msgstr "" + +#: ../../content/applications/studio/views.rst:187 +msgid "" +"To add information from other fields, select them under " +":guilabel:`Additional Fields`." +msgstr "" + +#: ../../content/applications/studio/views.rst:188 +msgid "" +"To have a route suggested between the different records, tick " +":guilabel:`Enable Routing` and select which field should be used to sort " +"records for the routing." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Task model's Map view" +msgstr "" + +#: ../../content/applications/studio/views.rst:199 +msgid "Timeline views" +msgstr "" + +#: ../../content/applications/studio/views.rst:202 +msgid "" +"When you first activate one of the timeline views, you need to select which " +":ref:`Date ` or :ref:`Date & Time " +"` fields on your model should be used" +" to define when the records start and stop in order to display them on the " +"view. You can modify the :guilabel:`Start Date Field` and :guilabel:`Stop " +"Date Field` after activating the view." +msgstr "" + +#: ../../content/applications/studio/views.rst:213 +msgid "Calendar" +msgstr "" + +#: ../../content/applications/studio/views.rst:215 +msgid "" +"The :guilabel:`Calendar` :icon:`fa-calendar` view is used to overview and " +"manage records inside a calendar." +msgstr "" + +#: ../../content/applications/studio/views.rst:218 +msgid "" +"To create records directly within the view instead of opening the :ref:`Form" +" view `, enable :guilabel:`Quick Create`." +msgstr "" + +#: ../../content/applications/studio/views.rst:222 +msgid "" +"This only works on specific models that can be *quick-created* using only a " +"*name*. However, most models do not support quick creation and open the " +":guilabel:`Form` view to fill in the required fields." +msgstr "" + +#: ../../content/applications/studio/views.rst:226 +msgid "" +"To color records on the calendar, select a field under :guilabel:`Color`. " +"All the records sharing the same value for that field are displayed using " +"the same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:230 +msgid "" +"As the number of colors is limited, the same color can end up being assigned" +" to different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:233 +msgid "" +"To display events lasting the whole day at the top of the calendar, select a" +" :ref:`Checkbox field ` that specifies" +" if the event lasts the whole day." +msgstr "" + +#: ../../content/applications/studio/views.rst:236 +msgid "" +"To choose the default time scale used to display events, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Default Display Mode`." +msgstr "" + +#: ../../content/applications/studio/views.rst:240 +msgid "" +"You can also use a :guilabel:`Delay Field` to display the duration of the " +"event in hours by selecting a :ref:`Decimal ` or :ref:`Integer ` field on " +"the model which specifies the duration of the event. However, if you set an " +":guilabel:`End Date Field`, the :guilabel:`Delay Field` will not be taken " +"into account." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Calendar Event model's Calendar view" +msgstr "" + +#: ../../content/applications/studio/views.rst:254 +msgid "Cohort" +msgstr "" + +#: ../../content/applications/studio/views.rst:256 +msgid "" +"The :guilabel:`Cohort` :icon:`oi-view-cohort` view is used to examine the " +"life cycle of records over a time period. For example, it is used in the " +"Subscriptions app to view the subscriptions' retention rate." +msgstr "" + +#: ../../content/applications/studio/views.rst:260 +msgid "" +"To display a measure (i.e., the aggregated value of a given field) by " +"default on the view, select a :guilabel:`Measure Field`." +msgstr "" + +#: ../../content/applications/studio/views.rst:262 +msgid "" +"To choose which time interval is used by default to group results, select " +":guilabel:`Day`, :guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` " +"under :guilabel:`Interval`." +msgstr "" + +#: ../../content/applications/studio/views.rst:264 +msgid "" +"To change the cohort :guilabel:`Mode`, select either :guilabel:`Retention` " +":dfn:`the percentage of records staying over a period of time, it starts at " +"100% and decreases with time` or :guilabel:`Churn` :dfn:`the percentage of " +"records moving out over a period of time - it starts at 0% and increases " +"with time`." +msgstr "" + +#: ../../content/applications/studio/views.rst:268 +msgid "" +"To change the way the :guilabel:`Timeline` (i.e., the columns) progresses, " +"select either :guilabel:`Forward` (from 0 to +15) or :guilabel:`Backward` " +"(from -15 to 0). For most purposes, the :guilabel:`Forward` timeline is " +"used." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Subscription model's Cohort view" +msgstr "" + +#: ../../content/applications/studio/views.rst:280 +msgid "Gantt" +msgstr "" + +#: ../../content/applications/studio/views.rst:282 +msgid "" +"The :guilabel:`Gantt` :icon:`fa-tasks` view is used to forecast and examine " +"the overall progress of records. Records are represented by a bar under a " +"time scale." +msgstr "" + +#: ../../content/applications/studio/views.rst:285 +msgid "" +"To prevent users from creating or editing records, untick :guilabel:`Can " +"Create` or :guilabel:`Can Edit`." +msgstr "" + +#: ../../content/applications/studio/views.rst:287 +msgid "" +"To fill cells in gray whenever a record should not be created there (e.g., " +"on weekends for employees), tick :guilabel:`Display Unavailability`." +msgstr "" + +#: ../../content/applications/studio/views.rst:291 +msgid "" +"The underlying model must support this feature, and support for it cannot be" +" added using Studio. It is supported for the Project, Time Off, Planning, " +"and Manufacturing apps." +msgstr "" + +#: ../../content/applications/studio/views.rst:294 +msgid "To show a total row at the bottom, tick :guilabel:`Display Total row`." +msgstr "" + +#: ../../content/applications/studio/views.rst:295 +msgid "" +"To collapse multiple records in a single row, tick :guilabel:`Collapse First" +" Level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:296 +msgid "" +"To choose which way records are grouped by default on rows (e.g., per " +"employee or project), select a field under :guilabel:`Default Group by`." +msgstr "" + +#: ../../content/applications/studio/views.rst:298 +msgid "" +"To define a default time scale to view records, select :guilabel:`Day`, " +":guilabel:`Week`, :guilabel:`Month`, or :guilabel:`Year` under " +":guilabel:`Default Scale`." +msgstr "" + +#: ../../content/applications/studio/views.rst:300 +msgid "" +"To color records on the view, select a field under :guilabel:`Color`. All " +"the records sharing the same value for that field are displayed using the " +"same color." +msgstr "" + +#: ../../content/applications/studio/views.rst:304 +msgid "" +"As the number of colors is limited, the same color can be assigned to " +"different values." +msgstr "" + +#: ../../content/applications/studio/views.rst:306 +msgid "" +"To specify with which degree of precision each time scale should be divided " +"by, select :guilabel:`Quarter Hour`, :guilabel:`Half Hour`, or " +":guilabel:`Hour` under :guilabel:`Day Precision`, :guilabel:`Half Day` or " +":guilabel:`Day` under :guilabel:`Week Precision`, and :guilabel:`Month " +"Precision`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Planning Shift model's Gantt view" +msgstr "" + +#: ../../content/applications/studio/views.rst:319 +msgid "Reporting views" +msgstr "" + +#: ../../content/applications/studio/views.rst:328 +msgid "Pivot" +msgstr "" + +#: ../../content/applications/studio/views.rst:330 +msgid "" +"The :guilabel:`Pivot` :icon:`oi-view-pivot` view is used to explore and " +"analyze the data contained in records in an interactive manner. It is " +"especially useful to aggregate numeric data, create categories, and drill " +"down the data by expanding and collapsing different levels of data." +msgstr "" + +#: ../../content/applications/studio/views.rst:334 +msgid "" +"To access all records whose data is aggregated under a cell, tick " +":guilabel:`Access records from cell`." +msgstr "" + +#: ../../content/applications/studio/views.rst:336 +msgid "" +"To divide the data into different categories, select field(s) under " +":guilabel:`Column grouping`, :guilabel:`Row grouping - First level`, or " +":guilabel:`Row grouping - Second level`." +msgstr "" + +#: ../../content/applications/studio/views.rst:338 +msgid "" +"To add different types of data to be measured using the view, select a field" +" under :guilabel:`Measures`." +msgstr "" + +#: ../../content/applications/studio/views.rst:340 +msgid "" +"To display a count of records that made up the aggregated data in a cell, " +"tick :guilabel:`Display count`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Purchase Report model's Pivot view" +msgstr "" + +#: ../../content/applications/studio/views.rst:351 +msgid "Graph" +msgstr "" + +#: ../../content/applications/studio/views.rst:353 +msgid "" +"The :guilabel:`Graph` :icon:`fa-area-chart` view is used to showcase data " +"from records in a bar, line, or pie chart." +msgstr "" + +#: ../../content/applications/studio/views.rst:356 +msgid "" +"To change the default chart, select :guilabel:`Bar`, :guilabel:`Line`, or " +":guilabel:`Pie` under :guilabel:`Type`." +msgstr "" + +#: ../../content/applications/studio/views.rst:358 +msgid "" +"To choose a default data dimension (category), select a field under " +":guilabel:`First dimension` and, if needed, another under :guilabel:`Second " +"dimension`." +msgstr "" + +#: ../../content/applications/studio/views.rst:360 +msgid "" +"To select a default type of data to be measured using the view, select a " +"field under :guilabel:`Measure`." +msgstr "" + +#: ../../content/applications/studio/views.rst:362 +msgid "" +"*For Bar and Line charts only*: To sort the different data categories by " +"their value, select :guilabel:`Ascending` (from lowest to highest value) or " +":guilabel:`Descending` (from highest to lowest) under :guilabel:`Sorting`." +msgstr "" + +#: ../../content/applications/studio/views.rst:365 +msgid "" +"*For Bar and Pie charts only*: To access all records whose data is " +"aggregated under a data category on the chart, tick :guilabel:`Access " +"records from graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:367 +msgid "" +"*For Bar charts only*: When using two data dimensions (categories), display " +"the two columns on top of each other by default by ticking " +":guilabel:`Stacked graph`." +msgstr "" + +#: ../../content/applications/studio/views.rst:0 +msgid "Sales Analysis Report model's Bar chart on Graph view" +msgstr ""